Same. On Google Docs it auto-corrects to an en-dash (–), which is annoying, but I find the double dash (--) more easy to spot and read on computer screens.
Also, cosmetically I don't really like how em-dashes are used without spacing (e.g. "this—then that" instead of "this — then that"). Feels like we're trying to import publishing styles from newspapers and books heavy on serif font to places where monospace and sans-serif is the norm and it doesn't quite fit well.
Interesting that in the US metamizole[0] (dipyrone, or Novalgin and Analgin comercially) is banned in the US due to agranulocytosis[1] risk. It's fairly common in Europe, Asia and South America.
NixOS has been my daily driver since 2022/2023 and I have greatly improved the management of my 2 computers and few VMs since. Because of LLMs, I now understand the language much better, but even if I didn't want to write Nix directly, describing the config to AI usually produces good results.
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
VLC is not the example you're looking for. Written in Qt for desktop and their own libVLC wrapper for mobile. Yes, in the case of VLC, parent comment is right: you clearly see the issue. And a media player is a relatively uncomplicated piece of software, UI wise.
Tons of great options, for sure, but community efforts and corporate sponsorship ends up fragmented if there isn’t a clear winner.
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?
The LCD screen polarizer may eventually detach[0][1], effectively ruining the screen. Unfortunately, it's not easily replaceable. I think it's not impossible the enthusiast community will eventually come up with a solution, but until then I'd use your 48G as much as you can. After it's done, either get a Prime while they still sell on eBay or get a SwissMicro 42n for similar keyboard feel and nostalgia factor.
Thanks for the write up. Wondering why not use something like Flutter for good cross platform support with good graphical performance on all systems.
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).
I always thought the problem with hybrids was the complexity of the drive train, but this video is challenging that notion. It argues that the hybrid pack (minus the battery, perhaps?) is more compact and simpler than a manual gearbox, even. It consists of two electric motors and a planetary gear set, which is seemingly simpler than clutch packs, gear sets and belts of regular transmissions, including CVTs.
Time codes 3:06, 37:07, 43:57, 43:36 (note on the eCVT naming), and 44:17.
I learned recently that Hitachi actually shipped computers that would dual-boot into Windows 98 and BeOS R4, except that Microsoft's license didn't allow for dual-boot, so the option was removed from the bootloader (or, rather, the Microsoft bootloader was defaulted to, instead of the Be bootloader).
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.
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.
The gaming laptops that have been made a bit less game-y without the RGBs and thick chassis turned out to be the sweet spot for me. Some compromises here and there, sure, but they mostly have the hardware I want. Asus has a good line up that works very well with Linux from 13 to 16 inches, all with dGPUs, AMD CPU (though Intel is also there), high-refresh rate OLEDs etc.
> fire mid-management and PMs to prevent the same thing from happening again
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.
For something portable with a dGPU, I recommend the Asus ProArt px13. Works very well with Linux, including NixOS with the right config, with the community asusctl and supergfxctl. AMD, OLED screen, nVidia 4070 (4060 in the US, maybe we'll get 50xx next year). Downsides: the keyboard is not amazing, it comes with MediaTek WiFi, but is replaceable, and the SSD is 2230, which limits capacity. I haven't been able to fine-tune touchpad sensitivity in Wayland and I do get some screen flickering despite fiddling with some boot params and being on 6.17.x. Fewer constraints if you're willing to go 14-inch with the Zephyrus.
I tried some scanning on a Plustek 8300, which is supposed to be the fastest. The process is still extremely manual/slow and I don't think it's practical on a large scale. Many families who owned cameras in the 60s-70s-80s-90s will have potentially thousands of negatives to scan, but I don't see a solution that will automate that digitalization process.
Software could also use some improvement. Automating batch correction and clean up should be easier, IMO.
Also, cosmetically I don't really like how em-dashes are used without spacing (e.g. "this—then that" instead of "this — then that"). Feels like we're trying to import publishing styles from newspapers and books heavy on serif font to places where monospace and sans-serif is the norm and it doesn't quite fit well.