https://world.hey.com/dhh/turbo-8-is-dropping-typescript-701...

[0] https://en.wikipedia.org/wiki/Metamizole

[1] https://en.wikipedia.org/wiki/Agranulocytosis

The two main sticking points IMO are still:

- Development environments are still a pain. devenv.sh is great for web and backend, but not perfect for dependency (package) management and more complicated environments like mobile or embedded

- nixpkgs monorepo doesn't update fast enough IMO. As a consequence, I see a number of flake repositories popping up to more easily package and distribute software not yet on nixpkgs or that don't update often enough (https://github.com/numtide/llm-agents.nix is a good example). This is perhaps by design, but it takes some digging to find the reliable and trustworthy flake repos. I'm increasingly concerned with AUR-like trust issues

For desktop app development, if I don’t care about native controls (and what does that mean in Linux or even post-Win32, anyway?) and don’t want to deal with Electron, why not use something a bit more established like Avalonia or Flutter?

[0] https://www.hpmuseum.org/forum/thread-18710.html

[1] https://www.reddit.com/r/calculators/comments/1r8gtvr/hp_48g...

One could argue that with agentic programming, releasing on a new platform is simply a matter of prompting for a new target, but I fear that the non-determinism of LLMs will lead into a whac-a-mole situation where you’re constantly fighting framework specifics and the code that the agent spit out to get to pixel perfect solutions across the platforms. Flutter in this case would be a more token efficient solution and quite fast on most platforms (particular the ones where their Impeller engine runs).

Time codes 3:06, 37:07, 43:57, 43:36 (note on the eCVT naming), and 44:17.

It wasn't that hard to boot into Be, but I suppose most users wouldn't bother because all games and applications were on Windows anyway. Ultimately, lack of apps was probably what held it back, although Microsoft's commercial practices definitely played a role in curbing OEMs and app developers.

* https://en.wikipedia.org/wiki/Hitachi_Flora_Prius * https://news.ycombinator.com/item?id=44217322

Problem with them, for the most part, will be about rebuilding the batteries and dealing with the poor quality of old screens.

* Limitations *

The data only contains the start and end station for each trip, but does not contain the full path. Route geometries are computed for each (start station, end station) pair using the shortest path from OSRM.

This means that the computed routes are directionally correct but inexact. Trips that start and end at the same station are filtered out since the route geometry is ambiguous.

Did Fischer ever make it outside of Germany? My father would bring us kits every time he would travel there for work in the late 80s/early 90s. The focus was more on Engineering themes, so not quite the same as a Lego or Playmobil set. More like Lego Technic for the most part.

Firing PMs and mid-management would not prevent any of code reds you may have read about from Google or OAI lately. This is a very naive perspective of how decision making is done at the scale of those two companies. I'm sorry you had bad experiences working with people in those positions and I wish you have the opportunity to collab with great ones in the future.

Software could also use some improvement. Automating batch correction and clean up should be easier, IMO.

PowerToys is not installed by default and neither is this Google app, obviously. It's absolutely reasonable that Google picks the most intuitive and common shortcut for an app launcher and if the user wants to maintain two or more launchers, it's up to them to configure non-conflicting keyboard shortcuts that are the most intuitive to them.