skysight-inc/HackerNews huggingface dataset:
"The advisory placed much of the blame on Versa customers who “failed to implement system hardening and firewall guidelines…leaving a management port exposed on the internet that provided the threat actors with initial access.”"

If ISPs are leaving management ports open on the Internet, it's going to take more than a vendor patch to protect them from cyber warfare.
Yeah, I just meant it is more similar to a property tax than an income tax. Of course the other difference is that you might be able to deduct the tax you paid if the value drops back down before the gain is realized... but I haven't heard enough of the proposed implementation details to sort that out.
> Pretty sure it's actually extremely interesting.

You missed the from an engineering perspective part at the begining of this sentence.
If 90% of new drugs fail to reach market, is drug research a waste of time?
That's exactly what a sentient AI would say to throw us humans off the scent.
What's to prevent corporations and the rich from taking advantage of this? ie, my job is $10k + rest in "tips"?
>”not yet”

“Because we still have suckers paying us large cloud bills for ancient hardware.”
I assume business would just lower the amount they pay, since tips would be worth more.
You don't want to expose details about your platform. Thousands (millions?) of sites have been compromised because errors caused them to dump public tracebacks.
I once picked up a theoretical math book about category theory. It's a lot of the mathematical basis behind data structures; and where terms like "class" come from.

Unfortunately, when I was in undergrad, my school and other schools didn't understand that most incoming students needed "software engineering" instead of "computer science." Although there is a lot of overlap; misunderstanding the intention and purpose of students made it very hard to learn the skills we were there to learn.
+1 Seen it many times where a new grad / jr. engineer exaggerates their skills to get a job and the greedy hiring manager thinks s/he has scored big time with a cheaper hire. Big mistake on both ends. Be truthful, do a thorough assessment and it will be a good match.
Ask HN: Git status, fatal iconv_open why?
git status

fatal: iconv_open(UTF-8,UTF-8-MAC) failed, but needed:

precomposed unicode is not supported.

If you want to use decomposed unicode, run

"git config core.precomposeunicode false"
> There is nothing about going to MIT that makes me think

That makes you think (no shade)... Question is: does it bother you enough to not proceed in engaging? Likely not. The upside is other audiences that love that kind of stuff - investors, other customers, individuals, etc.

Mostly neutral to positive, little negative.
This is a fine example of an insane conspiracy theory which nevertheless should not be censored.
Sorry, can't make that argument after Fukushima unless there is foolproof passive safety like a LFTR plug.

A problem with organizationally managed safety is just the human error problem, and two that human organizations come to resent and undermine regulations, particularly at the management level. This attitude is rite in the nuclear industry in America, and similarly from what I can tell from tepco management of Fukushima.

Nuclear needs a scalable price competitive meltdown proof full fuel usage reactor. I think LFTR, materials issues aside, is the solution, but possibly even that won't be able to compete long term with solar wind even with miraculous materials engineering.
Hello! Abhi here, We are building a design app for consistent, editable and brand-aware vector graphics. Give it a try and let us know your thoughts :)
You solve temporary overproduction with storage.

You solve permanent overproduction with mobbing people together and demanding that the government stops mandating it. Because it only exists when the government mandates it.

If you want to soften the blow into people that have to learn how to grow some completely different crop. You go and do that, you don't create an entire class entitled to permanent societal support for not working.
what do you think caused this? I was minding my own business in a normal repo then all of a sudden
There is argument against and in favour. France works like that and it means a lot of people don’t pay taxes and in return don’t feel very connected to the state spending. It’s weird but I think a token amount of tax completely offset by state handovers is preferable to no tax purely from a mind set point of view (you too are part of the collective and contribute to the working of the state).

The whole thing is a bit disingenuous anyway when so much of tax revenue actually comes from VAT and other indirect taxes.
Lifesight – Invest in Marketing with Confidence
Increasing the tipped minimum wage means that restaurants will add that cost to the menu. Because tips are based a percentage of your order, this means that customers actually pay more money in tips, even though these laws are marketed as reducing the need for tips.
"Simpler" is part of the problem. The "simplicity" is delivered by keeping more in the programmer's head and not writing it down in the C source code. But if you're not the original programmer (or you have since forgotten) that's much worse.

Trivial example would be the benefits of a richer type system: You have a TCP socket, a file descriptor, and a non-negative counter

In C that's an int, another int, an unsigned int

In Rust that's TcpStream, OwnedFd, usize

The C is simpler, there are only two types and they're both just integers. But of course in reality the more complicated Rust types model what's actually going on, these are not just integers, we shouldn't do arithmetic on an OwnedFd or a TcpStream, and we can't use a usize when we needed a TcpStream, they aren't the same kind of thing. In C that knowledge lives in your head as the programmer instead.

And I disagree in practice too, as a very experienced (decades) C programmer and a relatively novice (less than 5 years) Rust programmer I am much more confident contributing to a Rust project.
I would add that a lot of Borges' work is written in an academic style that is highly translatable, but he also wrote a lot about the criminal underworld in Buenos Aires and those works are, unsurprisingly, full of slang and local references that are much more opaque to outsiders.
So… if your ISP automatically updates your modems firmware, you may be backdoored
Completely agree. The vast majority of the failed projects fail at the planning stage. To put it simply, if the cost of a misprediction is high then it is usually not going to work because all models make mispredictions. This is something that can be identified in the planning stage i.e. it's usually completely avoidable. Also, of the 20% of projects that succeed, I wonder how many of them actually needed ML.
Look at the posting history of the comment posters, not just the comment.

In many cases it's not the particular comment, it's the particular poster who is shadow-banned, and all of their comments are dead on arrival (to everyone but themselves, the definition of shadow banned). But people with showdead=true and enough karma can vouch for them to resurrect them if they're worthwhile.
If they're all placebo, then yes.
8B is not exactly great for roleplaying, if we put the bar any high. It is just not sophisticated enough, as it has very limited "reasoning"-like capabilities and can normally make sensible conclusions only about very basic things (like if it's raining, maybe character will get wet). It can and will hallucinate about stuff like inventories or rules - and it's not a context length thing. If there are multiple NPCs, things get worse, as they're starting to all mix up.

70B does significantly better in this regard. Nowhere close to perfection, but the frequency of WTFs about LLM's output are [subjectively] drastically lower.

Speed can be useful in RP if we'd run multiple LLM-based agents (like "plot", "goal checker", "inventory", "validation", "narrator") that function call each other to achieve some goal.
The RISC dream was to simplify CPU design because most software was written using compilers and not direct assembly.

Characteristics of classical RISC:

- Most data manipulation instructions work only with registers.

- Memory instructions are generally load/store to registers only.

- That means you need lots of registers.

- Do your own stack because you have to manually manipulate it to pass parameters anyway. So no CALL/JSR instruction. Implement the stack yourself using some basic instructions that load/store to the instruction pointer register directly.

- Instruction encoding is predictable and each instruction is the same size.

- More than one RISC arch has a register that always reads 0 and can't be written. Used for setting things to 0.

This worked, but then the following made it less important:

- Out-of-order execution - generally the raw instruction stream is a declaration of a path to desired results, but isn't necessarily what the CPU is really doing. Things like speculative execution, branch prediction and register renaming are behind this.

- SIMD - basically a separate wide register space with instructions that work on all values within those wide registers.

So really OOO and SIMD took over.
I honestly find the lack of compiler/interpreter complexity disheartening.

It often feels like as a community we don't have an interest in making better tools than those we started with.

Communicating with the compiler, and generating code with code, and getting information back from the compiler should all be standard things. In general they shouldn't be used, but if we also had better general access to profiling across our services, we could then have specialists within our teams break out the special tools and improve critical sections.

I understand that many of us work on projects with already absurd build times, but I feel that is a side effect of refusal to improve ci/cd/build tools in a similar way.

If you have ever worked on a modern TypeScript framework app, you'll understand what I mean. You can create decorators and macros talking to the TypeScript compiler and asking it to generate some extra JS or modify what it generates. And the whole framework sits there running partial re-builds and refreshing your browser for you.

It makes things like golang feel like they were made in the 80s.

Freaking golang... I get it, macros and decorators and generics are over-used. But I am making a library to standardize something across all 2,100 developers within my company... I need some meta-programming tools please.
Why is it so gosh darned slow? If you've got enough transistors to hold 44 gigabytes of RAM, you've got enough to have the whole model in stored with no need for off-chip transfers.

I'd expect tokens out at 1 Ghz aggregate. Anything less than 1 Mhz is a joke.... ok, not a joke, but surprisingly slow.
You don't need to sacrifice the rigor to have a more balanced community, at least not at the total size Caltech is. There's a large component of college admissions these days that is somewhat arbitrary. High school resumes (at least the type that applies to these schools) have become absolutely cracked. Like it used to mean something to have a research internship, now it's weird not to.
It lowers the probability. It's well known LLMs have imperfect reliability at following instructions -- part of the reason "agent" projects so far have not succeeded.
Show HN: Minipic converts and compresses image in browser using WASM
I'm not sure this holds just by virtue of the system. For example Wikipedia uses a similar model and they are also heavily centralized, the majority of the moderation is done by a very small number of users. If anything, I would say systems like this naturally tend towards a small inner circle.
Did you reply to the wrong comment? This doesn't appear to have anything to do with what I wrote.
Enterprise customers don't like surprises; not even positive ones. This is a good way to lose trust.
Windows 11 has compatibility with 30 year old software. And will be able to be emulated far into the future.

If you are ending a product that users were using to make creative works, then preventing that product from working into the future is robbing the future of the ability to look back at these files.

Imagine a case where 5 years from now you find your backups with files from Finale. You won't be able to read them unless you have an active activated installation. Even if you had the installer backed up so you could re-install, it won't work.

The right thing to do, would be to enable the users to keep running this software, if they have the means + the rights, not activly prevent it from working. Especially if the only thing between a user and using their licensed software, is a license check.

Honestly, it's probably moot anyway: the pirate scene will almost certanly have the activation check patched out in no time.
I don't know what adversarial relationship you have with electricians, but adding more 220v outlets is absolutely feasible. Usually takes an electrician a day of work.
Right, I’m saying that if you’re looking at a roadmap and it’s vague then you need to give feedback and walk. Businesses are failing because of what you’re describing, hopefully the survivors have figured out more effective management strategies.
I wonder how common it was to be mortally injured by a breaking spear? If the spear is too heavy it's slow to move and less likely to result in a quick kill, if it's too light it'll break off without penetrating deep enough for a kill. Engineering trade-offs our ancestors must have pondered.
This does suck. I truly, honestly feel bad for you and other Finale users.

I might indeed be wrong (about what I’m not exactly sure yet despite your comment), but I think you maybe misunderstood my comment a little bit. I didn’t say the software will cease to exist, but the product actually went on life support yesterday and will cease to exist in a year. You can’t buy it, and support ends in 1 year. After that it no longer exists as a product. That’s not my opinion, it’s what the letter says.

It’s understandable to be upset about the new authorization cutoff. That might not be MakeMusic’s decision, it might be Steinberg’s. The move to Dorico and the discount on offer might be valuable and viable for a lot of people, but I have no doubt that it probably doesn’t work for everyone, and in that case the authorization shut-off hurts more.

But, new authorization isn’t going to help much beyond a year anyway, right? With the product dying, if you haven’t moved to something else by then, it’s just playing Russian Roulette. I’ve watched loads of Windows software become incompatible, software much younger than Finale, despite your point #2. I tried installing audio drivers for my Edirol audio interface just yesterday, and it no longer works. It sucks when software products you depend on go away, but unfortunately, people sometimes run out of money.
Interested in digging deeper, do you have a source for this:

> That's pretty hard to do when the absolute majority of the sum of taxes is paid by poor people. Even if you taxed the rich at 99%, it would be short by orders of magnitude
You mean the solar panel?

+ it is decentralized, cheap, low tech, low waste, easy to scale.
It is possible to teach math to this population, I've done it briefly when I was a teacher in an adult education school.

It's significantly slower than for average people and requires a ridiculous amount of effort on the part of the teacher and student, but it's possible.

Due to limited working memory many of these students will make mistake no matter how difficult the material is, and they will be slow at resolving problems, but I've never had a student without serious mental health issues be unable to get to precalculus level, and in the ones I've seen try they've been able to get to university math.

Again, many will always make more mistakes and/or be slow, but the concepts themselves are generally within grasp.
In theory it should be the cloud providers themselves maintaining the locally-runnable stand-ins for their services, but as it stands you basically either get it as a third party effort (MinIO for S3) or in cases where the service is just a hosted version of some existing OSS product (Postgres for RDS).

Either way, once the local version exists, then the job becomes maintaining all the infrastructure that lets you bring up the pieces, populate them with reasonable state and wire them into whatever the bits are that are being actively hacked-on.
I don't like tipping culture, but it does allow for wealthy people to subsidize service and incentivizes good service.

People that are more price sensitive tip lower and every once in a while a waiter will experience an extremely generous tip. I'm not convinced that forbidding tips would increase net wages paid to servers.

In terms of who is paying, restaurants will simply raise prices to account for higher wages. Their margins aren't that big.

Finally I think tipping definitely incentivizes good service. Its partly cultural, but I've noticed much higher level of service in the US compared to Europe were tips are not expected as much
I will maybe believe him maybe when they unban student groups like SJP Columbia.

https://x.com/ColumbiaSJP/status/1828099828301107294
The Laffer curve is just kind of made up. He just said "I believe this is how it should work" and then tried to make it work, even though it never quite does. And it often turns in results that its proponents don't like.
Was it an official act?

If yes, totally immune from consequences.

If not, then was it really "pressure"? In what sense?
Yeah, maybe unintuitive, but even if it costs more to collect and enforce taxes than you get from taxes, it also has a preventative side to not abuse it.
IAM role issues in Terraform modules
You could run an experiment pretty trivially to determine if the hardness of the water is the issue. Get one of those charcoal filters, get some coffee filters, and cook some rice with various combinations of the filtering.

The previous place I lived in had very hard water, and I found that running the water through both a coffee filter and then a Brita charcoal filter worked rather well to soften the water and improve the quality of the rice I was cooking.
The same is probably true for most kids the last 100 (or more) years. When I was 9 I was busy training to hit balls with a stick.
LLMs are extremely good at translation, given that the transformer was literally built for that.
> .. and this is the sort of hostility one attracts whenever one asks for transparency: the mask drops and the fangs come out.

Let me get this straight: you asking me to rationalize other people's actions is "transparency", but my asking you to explain your (in)action is hostility? It doesn't sound like you are contributing in good faith. Have a great day.
The 20% chance of success isn't typically 20% chance of a moonshot paying off, but rather of a project being successful and achieving it's cost saving/productivity and user acceptance goals.

I don't think your Kodak example works very well here - they were a classic business school case of not realizing what business they were really in, but most uses of AI (whether one means LLMs, or something else like most of your examples) are going to be automation/productivity enhancement, not "pivotal" changes.
What is needed is a shared identity with a vision for the future. Subsidies are good but not enough. It’s like the people who think America is a proposition nation: they never understood what made America great. A proposition can’t inspire anything that increases birth rates.
Moderators don't tolerate bigotry and racism on HN. I agree with that. But there were quite a few comments yesterday discussing Fyodor Dostoevsky who implied it was impossible for Russia to produce culture because it's people are monsters or something. Extreme ethnic hatred. So the users within the software community share many of the same faults regarding bigotry that the rest of humanity has.

Same goes for commentary on Chinese people or Palestinians, though nowhere near as extreme in animosity as that towards the Russian.
That's not exactly it; quite a few RISC-style instructions require multiple (sometimes many) clock cycles to complete, such as mul/div, floating point math, and branching instructions can often take more than one clock cycle as well, and then once you throw in pipelining, caches, MMUs, atomics... "one clock cycle" doesn't really mean a lot. Especially since more advanced CPUs will ideally retire multiple instructions per clock.

Sure, addition and moving bits between registers takes one clock cycle, but those kinds of instructions take one clock cycle on CISC as well. And very tiny RISC microcontrollers can take more than one cycle for adds and shifts if you're really stingy with the silicon.

(Memory operations will of course take multiple cycles too, but that's not the CPU's fault.)
I don't think this is spearheaded by the IRS at all.
How do I set up Git to thank future generations for removing code I regret checking in?
They're using TSMC 5-nm for WSE-3: https://spectrum.ieee.org/cerebras-chip-cs3
Is this the same as the distinction between an electrical engineer and a technician? That is, this is less about understanding the difference between coder/programmer, but understanding what people mean when they refer to technicians.

You see similar with cook versus chef. I'm sure the same distinction exists in near any work where a surprising amount of what needs to get done is far more mechanical than people admit.

It doesn't help that it is often loaded with loaded nonsense about worth.
Cerebras is known to use TSMC, so your speculation about boutique fab is incorrect.

https://cerebras.ai/press-release/cerebras-systems-smashes-t...
When you account for all taxes this may be true but for just income taxes it isn’t. According to the link below the bottom 50% makeup just 2.34% of income taxes paid. So, eliminating income taxes and maybe adding a return free filing option for the bottom 50% of households looks super doable.

Source: https://www.ntu.org/foundation/tax-page/who-pays-income-taxe...
Why you want to create cyclic reference from child to parent instead of a bare pointer?
Your conspiracy theory makes the flat earthers look like Rhodes scholars.

Seriously, you are out of your mind.
IMO it's just bad policy all round without a significantly higher level of detail. For example, how do we classify a tip vs a wage? If we're not very, very specific about it's going to be yet another tax loophole exploited by the rich who will pay each other $1 for work and then 'tip' thousands more.

Sure you’re an engineer on staff now but wouldn’t you want to be a freelancer, paid minimum wage and then a healthy “tip” every two weeks? Win win: I don't pay for benefits, you don’t pay tax.

No tax on tips can be sold as a benefit to the working poor while the small print can be written to favor the rich… no wonder politicians of all stripes are clamouring for it.
I think (hope) the expectation is to eventually increase wages and prices and phase out tips altogether. Tip culture has gone insane...even my home inspector's last invoice has a tip line!
Not really, you can't easily revert high volatility negative EV strategies, the transaction fees and interest will kill you.
This effectively means we've just nationalized 25% of all companies (over time as this tax spreads to more people).
Searle's argument in the Chinese Room is horribly flawed. It treats the algorithm and the machine it runs on as the same thing. Just because a human brain embeds the algorithm within the hardware doesn't mean they are interchangeable.

In the Chinese Room, the human is operating as computing hardware (and just a subset of it, the room itself is substantial part of the machine). The algorithm being run is itself is the source of any understanding. The human not internalizing the algorithm is entirely unrelated. The human contains a bunch of unrelated machinery that was not being utilized by the room algorithm. They are not a superset of the original algorithm and not even a proper subset.