ElectricSpoon

Those football playoffs are really getting out of hand…

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

For another platform to rise, there needs to be some heavy market shift. There already were opensource mobile OS: Maemo/meego/Tizen. Heck! I'd even throw phosh and ubports in the pot. But those are about as rare a sight in the wild as lightphones.

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.

On the flip side of cancellation, I wonder how much people cancelling are hurting themselves by sticking to retaliation.

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

What I truly appreciate is the completion system from a dev perspective. Writing completions is comfortable. Even wrapping completions into other completions is fairly clean (e.g. sudo {cmd}TAB).

> people thinking that taking Ozempic is a personal failing

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.

This reads like someone which had bad management using effort estimates as hours and bugged the team about it. I'm saying that having seen plenty of environments where they do Scrum wrong.

> 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.

Having read that, I really wish to back to being GM and trolling players by awarding them non-fungible plots of land as rewards. Then players get challenged since they failed to occupy the land, so at a later visit, they discover their plot occupied by squatters.

I find editors to be deeply personal things. Throw a vim user in vscode and you might be disappointed, and vice-versa. I don't care about your tools, I care that the sum of you and your tools make you good.

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.

Quebec does have a few. Amongst the issues is that scaling hydro power is hugely expensive, is riddled with red tape, and over all takes too long. Meanwhile you could build a datacenter and a solar farm in Texas and be up in 2 years.

They do tell you that you are missing now. On ubuntu 24.04, apt now reports/nags me about security updates behind esm-apps.

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/

I'm with you on that. Many argue that AI models don't "contain the code" but if they are trained on the copyrighted data, and generate something similar, then the AI model is akin to a lossy data compression format.

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.

WSL is alright. The real MVPs are the linux distros which have been building and shipping everything for arm64 for ages, and which happen to run on WSL.

From a cynical atheist point of view he's not wrong:

- 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"

> Wasm makes it thinkable to do DOM programming in languages other than JavaScript

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.

> runas allows you to run programs as other users, including but not limited to as administrator. This funtionality is on the roadmap for the sudo command, but does not yet exist.

Seems like it's not an alias.

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

When I look the hardware in it, I feels like the pinephone is just a step above what I would have built from a 3d printer, custom PCB, a microcontroller and an IOT modem from sparkfun. Every part is average, but the sum of it allows calling and has a usable idle battery life.

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.

> I would guess the developers wanted to prevent laptops running out of battery too quickly

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.

Meanwhile, I'm using noscript like it's still the 90's and get no such prompts. Granted most of the websites are crippled, but you can't have your cookie and eat it too.

A less known feature of some crosswalk buttons is that some have accessibility features. I've seen a few that were pointless when pressed due to automatic triggering. Long-press and you'll get longer time and an audible indicator while crossing.

My fear is that more AI will hinder our ability to literally search for stuff. The future I dread includes more profiling, a stronger search bubble, all of which will just make it the death of the objective search engine. As fascinating as AI can be, I don't think it's what search engines are missing. That is certainly not what I need.

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.

I see things the opposite way; you don't have to subscribe to everyone's blog. Proficiency comes with practice, and that inevitably means writing lower quality content, until you write better. Writing can be therapeutic. Sorting ideas and concerns to fit publication can give you another perspective. Acting on ideas can help memory. There are a ton of good reasons to write (to the void), so please write!

> Mass layoffs give you the opportunity to quickly purge poor performers

That would be true for poor performing projects. Try a bunch of projects; many don't take off; cut the chaff all at once.

What I've seen in various companies were cuts of all kinds of employees, regardless of their individual performance. Large cuts weren't about the employees but about the projects or teams. I've also lived through a cut which was basically reducing headcount across all teams. Cutting 11k employees isn't a micro-management thing; individual performers get hit all the same.

The fallback of some such cuts was that it took years to later re-acquire competent employees, especially since they were offering work conditions average for the market.

TLDR don't stay too long on projects or teams which aren't lucrative for the company, unless they are fun and you don't mind getting ejected from the company when cut comes.