Oh, ubuntu beem making decisions that many users think make things worse since it was first released
and yet it's still quite popular
2,814 karma · joined August 2, 2019
Oh, ubuntu beem making decisions that many users think make things worse since it was first released
and yet it's still quite popular
I see lots of value in adopting them, but the dsl's that they use are inscrutable to me. I'm sure that after some hands-on time I'd understand them well enough, but having a hard time figuring out how to get that ball rolling.
do: - use a different shape, or font/font weight.
- provide text labels that appear on hover
As a person with adhd, why would i want to sue my provider? They have nothing to do with why there's been an adderall shortage since october. it seems to me the last thing I want to do is make providers feel averse to treating adhd out of concern for being sued.
Can you give a concrete example of this behavior? I'm sure I can think of some, but I'd like to be more clear on what you had in mind.
Doesn't that just kind of describe google now though?
- Make police get individual insurance, similarly to doctors. Malpractice should have a monetary impact that doesn't hurt the taxpayer.
- A mirror to the DA, exclusively for prosecuting crimes committed by police. Remove the conflict of interest with the current DA system.
- Make police have some form of practitioners license, and have a board that can revoke it, similarly to the BAR association.
- Mandatory N years of desk duty after being involved in a fatal shooting (regardless of justification)
I love working with bash, but it has some footguns that really require an expert hand.
I know bash as-is will always be around for backwards compatibility with the god-knows-how-many scripts out there. It'd just be nice if there were a widely embraced path forward that kept the shell scripting spirit while shedding some of the unintuitive behaviors
Basically: a slice is a triple of {ptr to allocation, number of elements used, size of allocation}
the slices will share the same underlying allocation. By specifying the third parameter in the slice function, you set the capacity equal to the number of elements in your slice. This forces the next append to reallocate and copy the contents into a new region.
Without bounding the capacity when creating a new slice, the append operation could possibly continue using the same allocation, shared with the original slice. It could possibly resize and copy as well. It depends on how full the slice is, and is an implementation detail subject to change between versions.
> It is random sampling. I feel, 1M or 10M randomly sampled requests should cover all cases.
1. I suggest providing alternate approaches to sampling: The input itself may have bias towards a single use case. If 70% of the input exercises the same code path, there's no benefit to having a uniform sample. Ideally it would be stratified amongst customers, or perhaps on other dimensions to allow for covering the most surface area.
2. Requests don't happen in a vacuum. They likely have data dependencies on prior requests. I recommend some way of sampling sessions rather than individual requests. Replaying the 3rd request in a series of 6 is likely just going to be exercising failure paths.
3. Behaviors may vary between requests with respect to time. If requests were sampled over a number of days but replayed within a short time period, there are behaviors that could differ from what actually occurs in production.
I didn't see any explanation on how results are determined. I think it's important to surface those types of details on the website. I'm not going to watch the video on it in hopes of learning.
What properties of the code need improvement or demonstrate what other should aspire to? -- Getting someone to really articulate that is quite difficult.
A major problem however is if there's not a collective understanding that "yes, if" is not a suggestion or consent for that condition to be actualized.
So it really should be "yes, if ..., however, that situation is very rare/cost prohibitive/high risk, so should be avoided"
There needs to be some way to unambiguously signal that something is a no-go, even if there are situations where it would be a good idea.
I'm looking forward to playing with it this week
My question is: In the case of component vectors like that, given that many operations wind up in operations like dot products, do the advantages still apply?
I don't have any experience programming with simd instructions specifically, so the memory access patterns get a bit murky to me.
The same goes for cuda, for example, which has a native float4 type. It's making row ordering so convenient, and going for SoA seems like you need to walk away from that.
if they're distributing under gpl, that means they 1) have to make the source available, 2) the user maintains the ability to redistribute.
So provided that the user makes their own apt repo, they should be able to distribute it to as many machines as they see fit. That's essentially how centos operated. I'm sure there's some exceptions, around assets that ubuntu may own or any trademarks. But I shouldn't be learning this from an HN link to a twitter post of a screenshot that references ubuntu.com/pro. So I have the sense they haven't done much if any advertising for it? Maybe I've just been oblivious?
It is somewhat concerning that they're kinda holding security packages hostage...but I don't think it's unreasonable for ubuntu to want corporations to chip in. Gotta keep the operation running somehow, and bills don't just pay themselves. I don't know what else they can offer to make anyone actually shell out some cash.
one political party is flirting with authoritarianism, denying election results, pushing bigoted policies, marching with tiki torches, taking away all social safety nets, repealing abortion, refusing to do anything about healthcare insurance or even insulin prices, refusing to take any action on gun violence...oh, and insurrection.
It begs the question, who would want to willingly work with anyone endorsing that party?
In a sane world, we wouldn't have to ask the question. We do not live in a sane world.
Just looking at the playlist, I'm surprised at how many lectures are focused around actual distributed databases versus purely on theory or algorithms
It really made...the interpretation of computer programs...click with me.
And there's a meta-circular evaluator designed to fit on the number of blackboards they had available. So that's cool.
https://ocw.mit.edu/courses/6-001-structure-and-interpretati...
Took me a moment to parse it properly that returning to the office is stalling.