skysight-inc/HackerNews huggingface dataset:
On 32-bit Windows, segmentation registers still exist, but they are almost always set to zero. CS (code segment), DS (data segment), ES (extra segment), and SS (stack segment) are all set to zero. But FS and GS are used for other purposes.

For a 32-bit program, FS is used to point to the Thread Information Block (TIB). GS is used to point to thread-local storage since after Windows XP. Programs using GS for thread-local storage won't work on prior versions of Windows (they'll just crash on the first access).

X64 made it even more formal that CS, DS, SS and ES are fixed at zero. 32-bit programs running on a 64-bit OS can't reassign them anymore, but basically no programs actually try to do that anyway.

---

As for shorter types of pointers being in use? Basically shorter pointers are only used for things relative to the program counter EIP, such as short jumps. With 32-bit protected mode code, you can use 32-bit pointers and not worry about 64K-size segments at all.

---

Meanwhile, some x64 programs did adopt a convention to use shorter pointers, 32-bit pointers on a 64-bit operating system. This convention is called x32, but almost nobody adopted it.
I use this.

https://www.amazon.com/American-Crew-Precision-Blend-Hair/dp...

It’s a temporary hair color, which tends not to damage your hair. I find it lasts about a month.
Brilliant single line that is better than every other description above. Kudos.
sure, will add reordering! it's on the bucketlist, just needs fixing bugs first
What happened here is a specific scam where companies are targeted for ADA violations, which are so vague it’s impossible to “comply”.
Original author here. Thanks for sharing!

I see various comments below along the lines of “oh, the article is missing so and so”. OK… then please see the other articles in this series! I think they cover most of what you are mentioning :-)

The first was on EMS, XMS, HMA and the like: https://blogsystem5.substack.com/p/from-0-to-1-mb-in-dos

The second was on unreal mode: https://blogsystem5.substack.com/p/beyond-the-1-mb-barrier-i...

The third was on DJGPP: https://blogsystem5.substack.com/p/running-gnu-on-dos-with-d...

And the last, which follows this one, is on 64 bit memory models: https://blogsystem5.substack.com/p/x86-64-programming-models

Some of these were previously discussed here too, but composing this in mobile and finding links is rather painful… so excuse me from not providing those links now.
RH and chrismessina.me yay.
Are you sure? Maybe I only borrow the car.

Edit: I apply the same rule to FOSS, of course. If it can't idle or if it freezes up or crashes sporadically or whatever I remove it. I'm old, I don't have the patience for stuff that breaks without good reason.
> I'm having trouble understanding how else this is supposed to be? I understand that live migration is a thing, but even in those cases, a VM is "hardwired" to some physical server, no?

You can run your workload (in this case a VM) on top of a scheduler, so if one node goes down the workload is just spun up on another available node.

You will have downtime, but it will be limited.
That's just quibbling about the details of moving data from point A to point B. You're inventing a new protocol either way.
Yes, App Platform. Pricing is a little higher but way lower than AWS but it is fully justified. Zero downtime in the last 1 year.

With Fly, we had 3-4 downtimes in 2023 in a span of 4 months.
It’s basically a 10% increase in consumer prices for most goods, so…that has to stoke a few points of inflation. Not enough to move production back to the USA, since that would cost even more money, we just pay more.

The Mexico/Canada tariff is weird since we would basically be drastically curtailing business with our biggest trading partners, which is not in any way one way. He says it’s fentanyl related…it’s definitely not something you’d come up with sober.
https://archive.is/SNGSo
You can 3D print it and attach it to a boiling kettle.

https://www.youtube.com/watch?v=Z33HIAFuKoQ
Growing x100 times the amount of food needed isn’t ‘slack’, its production for export (or feeding pigs to export). We could cut out farmland by 50% and still have more than enough to feed our own population. This food security argument would only hold if there was any possibility of us actually not being able to feed our population.
That reassurance seems to rest on two extremely shaky assumptions:

1. That the first "10%" move move by the US is the only move anybody ever makes, one trade-battle that ends the entire potential trade-war in one fell swoop, as if all other countries are just too dumb/meek to retaliate.

2. That US tariffs will be implemented as totally flat rate uniformly across everything, rather than being concentrated to cause domestic winners and losers. (10% tax on 100% of items is very different than 100% tax on 10% of items.)

Neither of those were true last time. Rather than overall prosperity, tariffs paid by US consumers just became a subsidy ("forced redistributive welfare", if you like) for US producers. [0]

[0] https://www.cfr.org/blog/92-percent-trumps-china-tariff-proc...
just fixed this! please try again :)
I've always just used the Bookmarks page with a link to my calendar & tasks as the new tab, in addition to whatever classes/programs/events I need quick access to
If you run a SaaS and want to rapidly build out a CLI that you could plug into this ~and~ want something that humans can use, check out the project I’ve been working on at https://terminalwire.com

tl;dr—you can build & ship a CLI without needing an API. Just drop Terminalwire into your server, have your users install the thin client, and you’ve got a CLI.

I’m currently focused on getting the distribution and development experience dialed in, which is why I’m working mostly with Rails deployments at the moment, but I’m open to working with large customers who need to ship a CLI yesterday in any language or runtime.

If you need something like this check it out at https://terminalwire.com or ping me brad@terminalwire.com.
The article has about equal time about what Cybertruck owners dont care about, safety, reliability, etc.

> Similar to other critics (earlier this year, a CNN reviewer called the pickup a “disturbing level of individual arrogance in hard, unforgiving steel”)—Drury believes Cybertruck buyers are people “who think ‘I don’t care if I kill people when I drive this thing down the street,’” he says. “There aren’t many of those people out there, so there’s a relatively small market for the Cybertruck.”

The Josh Johnson on this one is gonna be good.
Headings don’t count as the body text
It’s worrying to me that Carbon separates data races and memory safety as two distinct things when data races can easily cause both spatial and temporal memory safety issues. Similarly, type safety, can also cause spatial issues (e.g. many kernel exploits in Darwin were a result of causing type confusion for the SLAB allocator resulting in an exploitable memory safety issue).

The entire philosophy errs too much in the direction of “being reasonable” and “pragmatic” while getting fundamental things wrong.

> Over time, safety should evolve using a hybrid compile-time and runtime safety approach to eventually provide a similar level of safety to a language that puts more emphasis on guaranteed safety, such as Rust. However, while Carbon may encourage developers to modify code in support of more efficient safety checks, it will remain important to improve the safety of code for developers who cannot invest into safety-specific code modifications.

That’s really just paying lip service to Rust without recognizing that the key insight is that optional memory safety isn’t memory safety.

It is kind of neat just how much Rust has managed to disrupt the C++ ecosystem and dislodge its position.
The article notes that the most recent recall was a physical one, not a software update, and implies that that was unusual.

I wonder if you exclude "recalls" resolved by software updates, for all cars, where it would rank then?
Deno is probably not "fully" NPM compatible, arguably, because you still need to prefix imports with "npm:" in a lot of cases. I've filed PRs to that effect, is why I know -- a breaking change for many widely-deployed libraries that need to maintain older node compat. That should not be necessary for a runtime that is "fully" NPM compliant.

Aside from that, Node compliance is a much larger ball of wax than simple NPM compliance, and as far as I know Deno is not there and will not be there for some time.

My gripe with Deno is the choice to hard-fork. That is core to the idea; so, we will disagree. No big deal. As a result of Deno's choice, people now have many runtimes to choose from: Bun, LLRT, and the one I have written on top of GraalJs, Elide. Many others, too.

Most of these runtimes shoot for as full NPM / Node compat as they can muster without intolerable contortions in the code. Why? Because a ton of software out there runs on NPM, or on Node APIs. Users think of server-side JavaScript and Node as the same thing -- this is not true, Node is both the "Node APIs" and the V8-based engine underneath it.

But this is exactly what I mean: for Deno to claim that Oracle does not "use" the JavaScript trademark requires a completely ignorant stance about technologies like GraalJs. Last we benched, Elide (on top of GraalJs) outperformed Deno by a wide margin. Oracle has invested years of engineering work into it. Enough that it outperforms Node (by a long shot) and Deno, and typically ties with Bun. So why does Deno get to say what happens with the trademark? It makes no sense to me.

I might even agree that Oracle should not own it or control it the way they do. I don't know. But I do know that Deno's demands are Node-centric, and the JavaScript ecosystem is simply way bigger than that.
> some commentators speculated that they thought Apple wouldn't build a compatibility layer at all this time around.

Unlike the PPC and x86 transitions? What was the rationale for such speculation?
it is all things but diverse

https://en.m.wikipedia.org/wiki/Ethnic_groups_in_the_Middle_...
A touchscreen laptop, I thought it would be incredibly useful and fun back when they were getting popular, but when I got one, I completely stopped using the touchscreen after a few months. I just didn't find it useful.
OT, but I can't not notice the wild domain.
They told it quite aloud in the last earning call. Quite funny how the market is selling NVIDIA on this news, does no one pay attention?

Conversely, TSMC trading down makes no sense. Who is going to make these ASICs? Surely not Intel.
Shame, was actually considering this:

https://www.amazon.com/dp/B0BNM56PF5
I'm going to call bullshit on his definition of this as being the first ever suburb. He defines it just such so that it fits his narrative but if we define a suburb as a mostly "outlying district of a city, especially a residential one". Then suburbs are just about as old as large cities.

Take ancient Rome for example. The formal city of the Republic was built inside the Servian wall, but what were essentially suburbs formed rapidly outside this boundary and spread widely, with residential and commercial districts. The later Aurelian wall covered these too, but again, further suburbs spread beyond that as well.

The article loosely argues that suburbs are defined as being planned outlying communities with middle class populations, but for one thing, this isn't a hard definition of them and secondly, such things also were the case as far back as antiquity.

Going back to the Rome example, many reasonably well-off people moved outside the city walls precisely to escape the dirty clog of the core, and even planned suburban industrial/business zones were created there. An example of these: the immense (even by modern standards) state/business-controlled Horrea Galbae warehouses for imported goods, well outside the older Servian walls of the city.

There's just no way I can think of defining such urban spread as anything but suburban growth, far, far before the 19th century.

edit: Just for a visual idea of what this Roman suburban district and those giant warehouses looked like, this image is a decent example. They were well outside the main urban area and truly were enormous, with well over 200,000 square feet of floor space, all inside a single massive building. http://www.galba.net/horrea_galbae.html
I first learned of this pasta from this video: https://youtu.be/O5JyezoCTJs Apparently they are up from 3 to 7 people who can make it now.
I worked in a huge docs website a while back and I’ll never forget the day I saw a request from a Redis lawyer that insisted we called it:

Redis™*

*Redis is a trademark of Redis Labs

The dumb thing is they insisted the footnote be on the first webpage Redis™ was displayed, as-if I had control over the order of the pages people viewed on the website.

Since then I’ve started removing Redis as a dependency from as many projects as I can.
Probably not related but these cartridges resembled 8-track cartridges which were also often referred to as (8-track) cassettes. It is easier to capitalize on slang than to make up a new word in marketing. Cartridge may sound too technical or even gun-like.
GM F-bodies (Firebird, Camaro) and the Corvette are good contenders as well. Barely counts but the C4 ZR1 Corvette (launched in 1989 for the 1990 model year) that made 375HP and was partially designed by Lotus would be up there as well. Taurus SHOs are quite popular now too. The Merkur XR4Ti was also a very cool car, and very cheap these days (mostly due to lack of parts availability without creativity); stock they only made a max of 175HP, but (speaking from experience) the fuel injected and intercooled versions of those engines can make over 300HP with little more than "turning up the boost." (The 2.3 turbo was also available in the Fox platform in the Thunderbird Turbo Coupe, Mustang Turbo GT and SVO, and a few others.)

Foxbodies are the most accessible especially when it comes to parts availability, community knowledge, and to a lesser extent these days, price. Except for maybe Fieros, and they have the benefit of being cheap too, for the most part. The GNX is absurdly expensive now, for what it is, but Cutlass Supremes and regular Regals aren't - they're popular conversion and modification targets.

And of course, there's the DeLorean. Probably the car with the single largest cult following. They're terrible cars - unreliable, slow, poorly built, but people love them.

If it were me and money were no object, I'd be going for the C4 ZR1. I've driven every other car mentioned above, except the GNX, and the standard TPI C4s making 250HP/LT1 C4s making 300HP are a lot of fun. I don't think you can get much more 80s America than a nearly 400HP Corvette with a top speed of over 180MPH. The Foxbodies are fun, but they definitely feel sketchy once you start making any more power than stock unless you spend a lot of money on suspension work.

Of course if it were really up to me there were no time constraints, I'd own a 1990s Buick Roadmaster with the same LT1 as the standard corvette and a T56 manual conversion (insert something witty about "faux wood that I grew up with"). But I already do, so that's kinda moot ;)
The Meta Quest.

I gotta find an excuse to use this thing.
> However, the mastering supplied to Hi Res shops sometimes lacks that compression, so that is where you can hear the album with room to breathe.

I've almost never heard of Hi Res with a totally new master that wouldn't have been previously available as CD, to be honest. This isn't common, right?

> the SACD format allowed adding a layer for 5.1 surround sound

Well, yeah. Too bad I don't have a PS3 to rip the SACD layer =)
Did the tow truck driver lose their license?
Unfortunately the passive method is not very effective at blocking sound, 75% is only about 5 dB.
Blip? 365 has an ongoing incident since yesterday morning, european timezone. The reason I know is because I use their compliance tools to secure information in a rather large bankruptcy.
> Hi Res audio is snake oil designed to sell the same thing multiple times, period

There's a karaoke bar I go to with "Hi Res" logos on the speakers. These are basically MIDI files, in a loud bar atmosphere, who is going to hear the difference, haha.
Good point, but still, you are leaving the user with too much leverage on the underlying architecture, again from the OS’ perspective.

They way I’m considering this is, one could provide virtual time sources, removing the high resolution timers, where the OS has more of a coarse-grained timer. Not sure the implications, but if needed, one could add jitter or randomness ( Noise ) to the virtual timer values…

This would further prevent thread from running out of sync with the resto of the threads.

Further, one could also add a stack based shared memory model, LIFO would provide a highly predictable behavior from an application perspective. If you make it per process, the shared stack would then be confined to the application. No sure if possible ( haven given deep thought ) but the stacks could be confined to specific cache lines, removing the timing differences caused by cache contention…
At first glance it seems to be a proposed standard interface and protocol for describing and offering an external system to the function calling faculity of an LLM.
The proof is on the pudding, how performance critical do you consider Pluton firmware, network cards firmware supporting Azure workloads?

Two examples of stuff publicly rewritten into Rust.

Games are special that isn't what Windows security cares about in first instance, when TinyGlade is the first ever commercial success using Rust.

Yet most games are done with Unreal and Unity, and yes there is lots of C++ there, but is mostly Blueprints, Verse, C# on top, that large majority of studios reach for.
Exploring the Magic of 432 Hz: Building a Music Frequency Analyzer
> For role models, they have rap stars who sing about sex and drugs

Such topics should really be limited to the opera, Shakespeare, and ancient Greek drama – where they belong.
I’ve lived in California and Indiana for 20 years each and recently discovered this explanation isn’t satisfactory.

You’re right in how you describe California; however they do look fondly on personal agency for liberal topics like birth control, abortion, marriage, drug usage, pissing on sidewalks in SF, etc.

I’ve concluded that different states value different forms of agency, but for some reason when people start pointing fingers they claim the other state doesn’t value agency.
This feature is basically just a shortcut to copy paste text in the app.

I actually wouldn't mind having this in my mobile browser, assuming it works well.
Mount Muztagh Ata with Blue Avalanche Light [video]
> Firstly, it has been extremely common for albums to be sold with very compressed dynamic range, assuming the average consumer will be listening in noisy environments etc. However, the mastering supplied to Hi Res shops sometimes lacks that compression, so that is where you can hear the album with room to breathe

I had a friend who was extolling the virtues of Hi Res for the pop music he was buying so I asked him to send me a track, and it had the same brick compression as the standard iTunes version and sounded just as flat (I was hoping that even if it was compressed the same, the extra resolution meant that you could recover the detail, but there wasn't an audible improvement).

If that's what they want to sell, they need to create an actual term for that, like the audio version of "Director's Cut", not just sneak it into some random Hi Res releases and hope you find "the good ones" while the rest are snake oil.
The rules should bar contestents from saving entropy outside the payload of the file. Whether that's in a file name or some file system data structure or in some timing side channel is insubstantial.

And once you ban that, it's impossible from an information theoretic point to win the challenge.
Is the opposite possible? I mean to have the dependency resolver use a sat solver? Would it be faster/slower?
Completely unrelated to safety, these vehicles don't look like they are aging well. They are all completely new but the ones I am seeing on the road already look a bit beat up. That finish on them and their general styling emphasize every minor blemish.
Malloc/Calloc can fail even if they typically don't on most Linux systems. You should always check for null pointers before accessing the resulting buffer, which doesn't happen here. The connections() block is also never explicitly freed anywhere I was able to find in a quick search. That's allowed, but definitely bad practice.
I don't think the wording was unclear. It's obviously their own article.
C++ is not just C++ but also the C preprocessor, the STL, the linker, the C libraries and SDKs you can't help but depend on, the build system, the build scripts, the package manager, the IDEs and IDE add-ons, the various quirks on various platforms, etc. That's on top of knowing the code base of your application.

Being really good at C++ almost demands that you surrender entire lobes of your brain to mastering the language. It is too demanding and too dehumanizing. Developers need a language and a complete tool chain that is designed as a cohesive whole, with as little implicit behavior, special cases and clever tricks as possible. Simple and straight-forward. Performance tweaks, memory optimizations and anything else that is not straightforward should be done exclusively by the compiler. I.E. we should be leveraging computers to do what they do best, freeing our attention so we can focus on the next nifty feature we're adding.

Zig is trying to do much of this, and it is a huge undertaking. I think an even bigger undertaking than what Zig is attempting is needed. The new "language" would also include a sophisticated IDE/compiler/static-analyzer/AI-advisor/Unit-Test-Generator that could detect and block the vast majority of memory safety errors, data races and other difficult bugs, and reveal such issues as the code is being written. The tool chain would be sophisticated enough to handle the cognitive load rather than force the developer to bear that burden.
Very few others have recalls that can be done OTA. Even if it is just software, expect an hour to days at a service center to do the update, if the techs can figure it out.

For Tesla, the software recalls are nearly automatic (one click install, just like other update), such that few owners even know that their car ever had a recall.
"[...]opting out can take up to 30 days, while the feature is live now."

Typical.
Lyin' Ted
That's not "strange" to me. Object storage has been a long time coming, and it's still being figured out: the entirely typical process of discovering useful and feasible primitives that expand applicability to more sophisticated problems. This is obviously going occur first in smaller and/or younger, more agile implementations, whereas AWS has the problem of implementing this at pretty much the largest conceivable scale with zero risk. The lag is, therefore, entirely unsurprising.
Yeah, good thing that e.g. RV64 has RIP-relative addressing mode that can address anywhere in the whole 56-bits of available space with no problems, unlike the silly 8086 that resorted to using a base register to overcome the short size of its immediate fields.
I saw my first Cybertruck the other day. It looked less weird in person than I expected it.

It's a very different and new design. How many of the 91% we're comparing to are completely new designs. What's the correct benchmark?

Let's rewrite the headline. "A radical new EV design from Tesla, the Cybertruck, is already ahead of 9% of all 2024 vehicles in quality as it just ramps up production".

I'll likely never own this - not my style. But I can appreciate doing things differently and being successful at that. Getting those gas guzzling truck owners to go electric would be nice too.