Ref: https://news.ycombinator.com/item?id=43157000

Phones have become essential to daily lives and the catch22 is: companies won't support niche platforms for their apps and users won't switch until the apps are there. Android happened to get adopted before everyone started relying on mobile devices as computer substitutes. Unless a major player pulls out a Valve move and does with waydroid what Valve did with wine, I can't imagine the market changing significantly.

Go read about the psychology of forgiveness. There are some pros to "letting it go", when appropriate.

Considering our society is pushes us toward sedentary highly-caloric lifestyles, I'd say we're set up to fail from the get-go. Therefore the failing is systemic not personal. I wouldn't compare to individual health issues. You can't cure celiac, but you sure could reduce the obesity using policies to drive the food industry toward less-sugar/more-fiber.

> Because there are no sprints, you don’t have to worry about whether something fits into a sprint

I like fitting things into sprints. It forces tasks to be broken down into manageable items. If it's too big to fit, it's also probably ill-defined. Sometimes it goes over the sprint; it's alright; discuss during retro and learn from it.

> If an emergency arises, everyone pauses their work

You can still do that with Scrum. Scrum is a framework to estimate the effort and measure at fixed points in time. That's not an excuse to dismiss issues. Unless all of your work is unplanned, you can handle surprises AND estimate your leftover velocity.

I think the good middle ground is having both a canned environment and allowing candidates to use their own... Unless the job is about debugging production systems where only vi is available, in which case that interview might as well represent the actual job.

They also publish an oval xml for use with openscap tools to get a list of unpatched CVEs. The issue is not enough people know about those tools. https://security-metadata.canonical.com/oval/

Frequency signal data over an image are not the image, but no one argues a JPEG encoded copy of a PNG isn't the same image. I think the weights vs code are similar in that regard.

As for releasing weights, probably more if we're talking about AGPL code.

- god is an imaginary construct used to rationalize data points

- god is often used by humans to make decisions, whether backed or not by data

- god is overhyped

substitute "god" with "AI"

Does it really? AFAIK, if I want to do any kind of DOM manipulation in say, rust, I need bindings that will basically serialize calls to be done on the JS side. So with the current incarnation of wasm, I believe you're still stuck with JS.

Seems like it's not an alias.

[1] https://learn.microsoft.com/en-us/windows/sudo/#how-is-sudo-...

Such a collection of hardware can't realistically compete with mainstream phones which have very tight hardware and software integration to achieve the most performance with the least power draw.

It's a bad phone (and bad portable computer), but mine might work for as long as LTE and my desire to recompile exist. Schematics, opensource and spare parts being available are the crux of it. It's the phone for those wanting to build their phones and it's pretty good at that.

And I would guess sysadmins also don't like their logging facilities filling the disks just because a service is stuck in a start loop. There are many reasons to think a service failing to start multiple times in a row won't start. Misconfiguration is probably the most frequent reason for that.

Even today, engines rank your results by geoip, trying to be smarter than you ask them to be. Two individuals doing the same quoted search will get different results. Perhaps I'm just getting old, but I do miss when searching was a matter of writing a good query, not a matter of what the engine thinks you will want to ask next and what else might interest you.