Libxml2 segv when the input is large and the transform complicated was something of a surprise to me. Parsing xml is easy enough but I think implementing xslt is going to be a nuisance.
HN user
JonChesterfield
Compilers.
Currently, cuda to amdgpu. Product is at https://docs.scale-lang.com/stable/manual/how-to-install/, please email jon at spectralcompute.com if it misbehaves.
meet.hn/city/gb-Bristol
Socials: - github.com/JonChesterfield
That's the any type and the moving logic into json loaded at runtime features
This only holds if society manages to hang together, which in the age of military strategy written by AI is looking borderline.
It won't last. You need a good grade to find work after so handing out lower grades decreases applications next year.
On the plus side, high grade + long ago remains a signal.
Scale is a cuda implementation running on nvidia or amdgpu. Think nvcc semantics with template diagnostics by clang.
Nvidia including Spectral in their inception programs seems a big deal to me. It bodes well for the future of the cuda ecosystem.
If you'd like to run it, docs and download at https://scale-lang.com/. It's a clang fork with a bunch of libraries packaged. I'm on the dev team and always happy to hear from people.
Not imaginary. Eliding checks on nullptr and integer overflow were both implemented, shipped, miscompiled the linux kernel and grew flags to disable them. I expect there are more if one goes looking.
Well, you can't write malloc in conforming C, which hurts rather more than remembering to write bitcast as memcpy on char pointers.
Doesn't matter though because you aren't writing standards conforming C. You're writing whatever dialect your compilers support, and that's probably (module bugs) much better behaved than the spec suggests.
Or you're writing C++ and way more exposed to the adversarial-and-benevolent compiler experience.
The type aliasing rules are the only ones that routinely cause me much annoyance in C and there's always a workaround, whether if it's the launder intrinsic used to implement C++, the may_alias attribute or in extremis dropping into asm. So they're a nuisance not a blocker.
You too can solve maths problems by:
1. Generating enormous amounts of text
2. Persuading a mathematician to look closely at it
3. Announcing success if they conclude it is a proof
This is deeply disappointing relative to "chatgpt found a proof that isabelle verifies" or similar, especially the part where a mathematician spends (presumably hours) reading through the llm output.
I found a 5gbe one that claimed 60W, will power a phone but not the low power laptop I've got here. It probably isn't far off.
Ymmv. I've got a mix of cheap premade patch cables and some I crimped from solid core, all cat5e, all holding 10gbe totally happily. I suspect that only works because they're a meter or two long but that reaches across the rack.
It would do nothing. You'd get an increase in derivatives volume with the same underlying effect.
Anyone worked out how much hardware one needs to self host this one?
Get out seems an important priority. Good luck
Who makes the bar for "good at delivering tech" if the guy pushing spacex, starlink and tesla simultaneously doesn't reach it?
The existing work is all of software dev. The program did what it was told to do, not what people wanted it to do, is rather a lot of the profession.
This was _really_ surprising to me. What's the point of marking individual stores if it affects everything, not just that address. But yeah, what I can find online agrees that C++ has done this. Thanks!
I've stopped reading anything on blogs on the basis that it's now probably llm spew and life is too short for the signal to noise ratio that implies.
With the exception of things that places like HN seems to consider worth reading, which is why I'm looking through the comments to this and others to find recommendations.
Any computer you have ssh access to.
Don't give your code to Microsoft if you don't want them to have your code.
This setting will make no difference to whether your code is fed into their training set. "Oops we accidentally ignored the private flag years ago and didn't realise, we are very sorry, we were trying to not do that".
If it's a power of two, you don't need the branch at all. Let the unsigned index wrap.
Push:
buffer_[head] = value;
head_.store(next_head, std::memory_order_release);
return true;
There's no relationship between the two written variables. Stores to the two are independent and can be reordered. The aq/rel applies to the index, not to the unrelated non-atomic buffer located near the index.
It's obviously, trivially broken. Stores the index before storing the value, so the other thread reads nonsense whenever the race goes against it.
Also doesn't have fences on the store, has extra branches that shouldn't be there, and is written in really stylistically weird c++.
Maybe an llm that likes a different language more, copying a broken implementation off github? Mostly commenting because the initial replies are "best" and "lol", though I sympathise with one of those.
If you can get a megawatt into the car batteries without setting them on fire, that's game over for petrol cars. And for the other electric vehicles that haven't worked it out yet. Only reason I'm on petrol is unwillingness to wait an hour to recharge the car.
The rest of the infra is fine if that can be done. Array of batteries and/or capacitors at the supply point and draw continuously from the grid.
Most entertainingly run a diesel generator on site if that doesn't work out. Lines up well with basing them at the existing fuel stations, got the diesel supply already sorted out.
Put a bunch of solar near it when you can. Maybe sell back to grid, nice to have the extra capacity available.
All comes down to capital deployment at that point. Do the calculations on how much to charge for slow car charge vs fast charge, fallback to slow with an apology/discount when the infra is struggling etc.
Huge news. Iff the cars don't catch fire when plugged in.
"Fair" or "insane" ideas on price vary a lot between people. See also "competitive" salary on job posts.
You might think $10 an hour is fair. Or you might think $1000 an hour is fair. If the developers you're trying to contact can't guess where you are on pricing, they'll probably ignore you.
Nope. A direct connection from residential British Telecom line is fine.
_Lots_ of traffic. It's going to end up being the global Internet backbone.
Something similar here but aggregated instead of failover, see openmptcprouter or diy equivalent.
Bad idea. I would be very angry to discover I've bought this. Customer support are going to get shouted at and products returned.
An alternative is people install the software they choose to on the machines they're using. Optionally write a list of suggested programs down somewhere.
In that world, there is no central IT team pushing changes to machines and arguing with developers about whether they really need to be able to run a debugger.
I don't know how to keep windows machines alive. It's probably harder.
Well, all the machines in the current outfit are Linux as far as I know. Services are self hosted. Seems to be fine, teams et al run adequately in a browser for talking to people on other stacks.
Previous place had a corporate controlled windows laptop that made a very poor thin client for accessing dev machines. One before that had a somewhat centrally managed macbook that made a very poor thin client for accessing dev machines.
You don't have to soul bond to Microsoft to get things done.