devnullbrain

The Centre for Computing History may be interested

Infohazard warning:

C++ reference is one of these.

I'm a big fan of my Deck, but I think Steam-related software projects always have a distinctive low-level stink.

I use mine on a train that has Wi-Fi with a captive portal and attempting to join it makes the whole UI unresponsive. Using the overlay with a guide in a game always resets the scroll location. These are the kind of things I can live with, but also things I don't expect ever to be fixed unless Valve come out with some wholesale replacement for some overt new strategic goal.

I find this kind of advice underspecified. The people struggling the most to find work are juniors: what projects are big enough that the applicant would a) know and care about them and b) get a benefit out of the network but also c) have fruit low enough for a solo junior to reach?

I tried this way-back-when and ended up submitting fixes to projects that were open source but had no real path to accepting patches from people outside the cathedral.

Every one of those is the wrong angle

How do you see someone using this page?

Feature names tend not to be very approachable. They often use very precise terminology or refer to papers with names that are targeted for a very in-the-know population.

As an example, one of the features listed is '`constexpr` `std::shared_ptr` and friends'. You seem to have a search that can cope with backticks but this feature doesn't show up if I search for 'constexpr shared_ptr'. That can be solved technically, but the bigger problem is that this feature also changes things for `weak_ptr` - or 'smart pointers' as a concept.

I can't picture a situation where I end up wanting to know the status of that feature's implementation in isolation.

For what it's worth, cppreference isn't any better at this, since it doesn't have any notes on the addition of support for `constexpr`ness of either pointer type. But with enough will I can change that.

The elephant in the room is that AGI doesn't need ads to make revenue but a new Google does. The words aren't matching with the actions.

An adjacency matrix seems like they gave the example most likely to irritate the mathematically inclined and confuse the outsider. Nested array access isn't that unusual.

Everything moves pretty slowly

https://en.cppreference.com/w/cpp/compiler_support.html#cpp2...

It's kind of shocking when you finally find the features you heard about in conferences used in the wild.

FWIW it definitely is and that's why you'd really probably just get a function or macro converting coordinates into a single-dimension offset in older C/C++.

It depends on hardware but I've seen improvements of 100 times faster. There's data available for a number of examples if you search.

It looks like the LayoutPolicy template parameter lets you choose

You choose where you live and work

Agreed, it's hard to understand how much easier commuting by train is until you've done it. YMMV if your local service sucks.

>Preferably with evidence

Sorry, can't do that. But my take is:

There is a part of the population that are opportunistic freeloaders. People who don't have intrinsic motivation to do their work but do it to avoid the consequences.

I think it's a pretty big part of the population! And I also think that, while managers are likely to have encountered them, reaching a software development role (and then choosing to spend your spare time commenting on HN) filters out a lot of them. So there is a mismatch where managers want to defend against the freeloaders while the employees commenting here can't accept the lack of trust inherent in the mandate and won't countenance the micro-management needed to prove that trust would be earned.

I think it also partly explains why we've failed to see remote companies gain a competitive advantage in hiring. They have adverse selection for active freeloaders.

It's worse now, but complaints about offices as working spaces were constant pre-pandemic too. Complaining about it then made you seem a bit... wet.

But now the highest levels have brought the productivity benefits of RTO into their wheelhouse. So making the offices suitable also shouldn't be a responsibility punted to a relatively minor position.

They've done it with pay and they've done it with hiring.

>the normal behavior shareholders expect.

And for each CEO, those shareholders are mostly the same people.

It's easy to get sucked into thinking this is just the way the world works but really we've just enshrined a local and temporal phenomenon. Layoffs aren't a physical law. There are places and times where this would not happen.

Let me put my investor hat on: hiring at the top and firing at the bottom is a predictable inefficiency and represents a CEO failing at their responsibilities. You don't get to be a CEO and claim ignorance of market cycles.

The efficiency of private markets in action.

> fixed-length instructions seem really nice when you're building little baby computers, but if you're building a really big computer, to predict or to figure out where all the instructions are, it isn't dominating the die. So it doesn't matter that much.

The notebooks of TFA aren't really big computers.

I want to measure the device how I use it. Race-to-sleep and power states are integral to CPU design.

>We are what we pretend to be, so we must be careful about what we pretend to be.

- Kurt Vonnegut

and

>If a person has ugly thoughts, it begins to show on the face. And when that person has ugly thoughts every day, every week, every year, the face gets uglier and uglier until you can hardly bear to look at it.

>A person who has good thoughts cannot ever be ugly. You can have a wonky nose and a crooked mouth and a double chin and stick-out teeth, but if you have good thoughts it will shine out of your face like sunbeams and you will always look lovely.

- Roald Dahl

Yes but social media companies have helpfully made this experience unpleasant.

UK, FYI

You're leaving lengths of strong flexible wire lying around places where you walk and are worried you might get hurt? Uh, yeah!

>lights from other vehicles showed up alerting you to any possible danger.

When I started driving I preferred the dark for these roads because the lights let you 'see' hazard around a corner.

Headlights were worse then - and I hadn't seen a crash into a deer.

I haven't driven in other countries but from my experience I'm not sure this is translating to good driving on the road.

Jim Keller has a storied career in the x86 world, it isn't surprising he speaks fondly of it. Regardless:

>So fixed-length instructions seem really nice when you're building little baby computers, but if you're building a really big computer, to predict or to figure out where all the instructions are, it isn't dominating the die. So it doesn't matter that much.

Well, efficiency advantages are the domain of little baby computers. Better predictors give you deeper pipelines without stalls which give you higher clock speeds - higher wattages

Interesting but it would be pretty rough to implement. If you take a binary now and run it on a core without the correct instructions, it will SIGILL and probably crash. So you have these options:

Create a new compilation target

- You'll probably just end up running a lot of current x86 code exclusively on performance cores to a net loss. This is how RISC-V deals with optional extensions.

Emulate

- This already happens for some instructions but, like above, could quickly negate the benefits

Ask for permission

- This is what AVX code does now, the onus is on the programmer to check if the optional instructions can be used. But you can't have many dropped instructions and expect anybody to use it.

Ask for forgiveness

- Run the code anyway and catch illegal instruction exceptions/signals, then move to a performance core. This would take some deep kernel surgery for support. If this happens remotely often it will stall everything and make your system hate you.

The last one raises the question: which instructions are we considering 'legacy'? You won't get far in an x86 binary before running into an instruction operating on memory that, in a RISC ISA, would mean first a load instruction, then the operation, then a store. Surely we can't drop those.

Yep. Redundancy and headroom are antonyms of efficiency.

That ASUS motherboard is far from the cheapest available. If using it makes the user liable for failure, a large part of the market is unsuitable.

For both the cooler and the motherboard, AMD have too much control to look the other way. The chip can measure its own temperature and the conceit of undermining partners by moving things on chip and controlling more of the ecosystem is that things perform better. They should at least perform.