skysight-inc/HackerNews huggingface dataset:
Researchers tend to write pretty poor code, if any of the research papers I've read/read corresponding code for are any indication.

Obviously not trying to state anything deep here by over-analyzing that one point in his quote, but kinda funny his statement implies researchers write decent code.

Often I question the result of a paper due to how bad the code is. Many paper results cannot even be replicated by writing your own code following the papers description.

I agree more fundamentally with the fact that most people write low quality code if there aren't structures/patterns already in place to protect them from themselves. From that perspective, I agree with his point. Though I'm not a big fan of the implementation of the idea
Plutonium can only be sent through burner reactors as MOX fuel once. After that, the isotopes left are no longer suitable and have to be buried (or saved for fast reactors.)
Wolfram’s suite of software seems like it’d require very specialized support staff. Maybe the higher price point helps keep the customer support side of the business more maintainable?
approximately nobody defines open source as "you can see the source but you aren't free to fork it or modify it"

This is not the conventional meaning of the term, and has repeatedly been used as an avenue to attack the concept in general.

As a comparison, how happy would you be calling a system where you can only vote for candidates approved by a single leader a "Democracy". Under these standards, both the USSR and China are democracies.

The differences matter, it is not pedantry and it is not some organization enforcing "their definition" overtop of what people "commonly think".
Exactly what I was thinking. I would love this if it was just a list of options that you may consider changing.
Gerald Weinberg's Secrets of Consulting and Becoming a Technical Leader are worth a look, as is his The Psychology of Computer Programming.

Also Peopleware by Lister and DeMarco.
There’s plenty of video games that do this going back to 2003’s Karaoke Revolution - if not earlier. Plenty of other games and series followed suit including as Rock Band, Guitar Hero, Lips, SingStar. There’s plenty of mobile apps that work similarly. AFAIK they basically track your pitch and timing. I remember Lips in particular rewarding vibrato as well.

The algorithms as I understand them are grading you based on sustained pitch (adjusting for octave) and cadence. Generally they are easy to fool - you can basically say gibberish but as long as it’s within the expected parameters you’ll still get a good score.

They are still rather fun though if you enjoy that sort of thing.
>SINCE 2006, when Corning, an American glassmaker, developed Gorilla Glass to give Apple’s first iPhone a scratch-resistance screen

This editorial seems very Apple centric, not generic science centric.

Gorilla Glass 1 released in 2006, iPhone 1 released summer of 2007.
RIP? She's not dead, last I heard.
wonder if this is just because these places are operated/owned by older people who are used to an era where people called all the time? Norms might have been different then… but even if that’s the case, they should be aware of the current norms.
A commenter to that article (nolen) wrote:

> I was involved in adding this to PNGs in ~2011 or so. I don't remember the details but you've got this pretty much right.

> The reason was indeed performance: on the first retina iPads, decoding PNGs was a huge portion of the total launch times for some apps, while one of the two cores sat completely idle. My guess is that it's still at least somewhat useful today, even with much much faster single-thread performance, because screen sizes have also grown quite a bit.

Interesting that PNG parsing was a severe bottleneck a decade ago...
> I'd wager price, convenience (fast shipping, etc.), size, and design matter far more to a buyer.

That's true until having been poisoned suddenly matters more.

But laissez-faire and buyer-beware I guess. Who needs any safety regulations at all, when we can all live in a utopia where every purchase needs to be evaluated by every consumer for every possible way it could cause harm?
Here’s an advantage of chess.com that I haven’t heard discussed yet. When playing against the computer I can request hints when I’m stumped. If lichess supports this then I haven’t found it yet. As a mediocre player I find it very instructive.
Hint: nobody uses "new" in C++ anymore. All the C++ containers, and make_unique etc. know how to use local arenas.

I gather there has been some effort to get Rust library components aware of such things. Handling exhaustion in them is an interesting research topic.
That's a good option too, though in that case the tradeoff is that compiling to a single binary is a bit harder than in the other languages. Someone mentionned Scala too, which is even "higher level" than OCaml, but I think Scala has the issue of future/async (monadic) concurrency, and is even harder to compile to native. There are lots of options in that space, which is great!

> It also does not have the 100B$ garbage collectors of the JVM, which are a deal breaker, at least for me.

Can you expand a bit on that? I was under the impression that even with all that investment, Java code tends to be slower and more memory hungry than equivalent Go code.
He was governor during the financial crisis wasn't it? Sounds like it was necessary measures since Indiana can't finance debt per its own constitution.
Why your own HAL crate? What’s different between yours and the original nRF HAL?
You need an authority to enforce that the author isn't signing a timestamp that does not match the actual clock time.
Okay...and? I said that neither China nor Russia are good actors (when I said invasions, I meant active ones, but I get your point), however, the U.S. is worse.

-The Russian invasion of both Ukraine and Georgia, summed together, had a civilian deathtoll of 4000+

-If we throw in the first/second Chechen war as well, we get a TOTAL civilian deathtoll of ~70k+

The U.S. killed 500k+ CHILDREN (not even accounting for adult civilians) with its Iraq sanctions (before the invasion), this is just ONE country of the MANY countries the U.S. has been a participant in destabilizing in the last two decades (and we're not even talking about Korea/Vietnam/supplying Saddam with chemical weapons/Gulf War/South American interventions)

https://www.youtube.com/watch?v=RM0uvgHKZe8

If you want to look at it from a per capita standpoint, the U.S. has killed far, far more civilians than Russia has (not that this justifies even the death of a SINGLE civilian), but one must objectively come to the realization that the U.S. is the biggest force for civilian mass murder in the world.

You can dress it up as "it was for democracy and freedom", but I don't think anyone buys that anymore. They don't even sell it to us as that anymore, now its for "national security", which is the same excuse Russia and China make as well.
Applied Science did a video playing with one.

https://www.youtube.com/watch?v=KdfHVcU8U7U

There are some significant limits on what it can analyze, but it's terrific for learning about metal alloys.
>sometimes stabs you in the back when it's convenient for them

Your summary didn't support this analogy. I think you need to work on it.

You mentioned that the Republicans repeatedly "stabbed" the Democrats, front, back, I dunno. Then after at least a quarter century of escalation, the Democrats (may have) retaliated.

I'm not arguing about how to describe history, you can have it your way. But the summary and the characterization just don't go together.
I work at a place that has started using Rust for backend services lately and I enjoy it, but IMO using F# instead would have given many of the benefits with a lower on-ramp time for new devs and generally higher dev velocity…
Smash and Grab? Don’t Come to Arizona
> I wish there was more stuff like this out there about rust, something, anything to counter what feels like blind optimism and fanboy-ism for the language.

I use Rust and I also use C/C++ and other languages as appropriate for each situation.

The fanboyism is a huge turnoff for me, too. But the anti-Rust complaints are also getting old.

Really, I’m just getting tired of everything in software engineering being turned into a competition, as if we’re cheering for our chosen sports team and we can’t stand to see the other team win anything. So much online discussion is wasted on Intel vs AMD, Mac vs Linux vs Windows, Rust vs C/C++/Go, React vs Remix vs 10 other frameworks.

It’s getting really hard to extract actual useful info from these permanent debates when the fanboys from different sides pour in to compete.

The best resources I’ve found are from people who aren’t afraid to use multiple platforms and acknowledge that they all have pros and cons. If someone can’t describe something in terms of tradeoffs, they’re probably not trying to make an honest evaluation.
Those designs probably aren't in Altium. They're probably in something like Mentor Xpedition or Cadence Allegro.

This is why I suggest that Altium is likely to be the first victim.

The non-Altium proprietary systems have a lot of legacy to hold them in place (like parts database integration across your company). In addition, they do have some very advanced features around routing matched memory buses and the like.

If, however, your design doesn't need that, KiCad will cover you, and Altium won't bring anything you need to the table.
https://archive.md/y6SLN
Is it in dispute, that Gorilla Glass was developed for the iPhone? There's a famous story of Steve Jobs visiting the CEO of Corning, saying they needed the stronger glass in 1 year and when told "That's impossible" responded with something like "Don't be afraid. You can do it" and other such things. Called the reality distortion field, Steve Jobs was famous for convincing people that they could do the impossible.
Interesting, come to think of it I haven't seen any Winnie the Poo merch on there either.
> It really doesn't. It doesn't even have native support for bitfields.

Many people would consider C bitfields half-baked in the first place, given that the feature is well-known to be underspecified in a way that leads to compatibility/portability concerns. Is this really the kind of stuff that Rust should concern itself with?
Maxheap-Python3
https://github.com/mshelll/maxheap

python3 heapq library tweaked to a maxheap
If you run nightly you can already Box::new_in(thing, my_allocator) if that is what you want. Or indeed, if you want to keep Nathan here happy, you can even Box::try_new_in(thing, my_allocator) and get Errors when your allocator says it can't help you (which you likely won't ever bother handling meaningfully).

In the event you're as desperate for those last dregs of performance as the author of the "Why not rust?" article, (and let's assume you actually measured your performance problem before jumping to the step where you make everything more complicated and more buggy for no good reason?) you can even Box::try_new_uninit_in() and unsafely do all the initialization in place as needed yourself as you might do by default in C++.

Now, I don't know when Allocators will be stabilized, the Working Group has been making steady progress for some years now but this is a tricky business, witness the many languages that get it quite badly wrong...
IIRC, __restrict__ in clang and g++ does nothing when you write C++ code. It is there just for compatibility with C.
> If you actually sat and read it, you'd see that

Without this phrase, your comment would be far friendlier and also not break the HN guidelines.
Seems like the message of Lori Laughlin’s prosecution was received loud and clear.
I am the CEO of https://serpapi.com.

Please consider helping us support the EFF actions. Outside the obvious vested interests of our business, I truly believe scraping the web is a force of good and progress. And the EFF work in ensuring web scraping stays a legal practice in the Unite States has been outstanding. [1]

[1] https://www.eff.org/deeplinks/2021/07/eff-ninth-circuit-rece...
* Advocate strongly for microservices

* And redux / sagas

* Rewrite in rust

* 100% test coverage or reject PR

* The most elaborate git workflow you can find

* Bonuses based on completed
story points

* OKRs
https://woodidentification.net/about/

"Identifying wood is not easy for a number of reasons. First, there are hundreds of different species of trees in North America. Second, the wood of many species looks very similar, if not identical."
I would like to understand why you focus on the feelz. Of more importance are actual prices and money velocity.
US distrust of Huawei linked in part to malware update in 2012
As a replacement for C or C++ (except 3D games where the choice of language is dictated by the engine). Kernels, databases, CLI programs, toasters, native code Python modules, etc.

As a replacement for Go if you want a comprehensive type system instead of a skinny one.
We tried https://techcrunch.com/2021/06/14/supreme-court-revives-link...

(I was CTO of hiQ (technically still am I think))

contact me if you want to chat about scraping danbmil99 at gmail
Can you explain it plainly? I seems like there's a funny joke or irony in there but I don't have the experience to detect it properly.
You can also... just allow a copy to occur. My friend is always talking my ear off about how people are so afraid to copy a string in Rust, going through insane motions to avoid it, when there is some actual quadratic complexity somewhere else that's actually eating up time, whereas a single string copy is undoubtedly taking mere nanoseconds.
I have the same opinion.

The best thing about rust is that rust attracts more people to learn systems programming languages. And thus, there will be more system programmers.

Nowadays, young people favor application programming far more than system programming.

But the problem is there are not that many system programming opportunities.

Then they decided to rewrite the existing systems with rust. We can find a lot of these examples on GitHub. Who knows if it is just a moment of enthusiasm, and how long will it last?
I don't agree it is at the prototyping level... I think C++ is quite far ahead there than Rust IMO...

For a 'stable' production implementation after prototyping, I agree that the benefits Rust provides (if it compiles, it will either panic or work) are well worth it, and so longer-term, I buy that you probably will spend less time, but in my experience, things like not being able to specify default field values inline (you need to provide a 'new' function, or 'default' impl, meaning you then have very tightly-coupled parts in different places in the code) compared to C++11's member variable inline initialisation is very fustrating when in the early stages of prototyping, when things are changing a lot.

Similarly, as mentioned above - string handling, with as_str(), to_string(), String::new(), from(), etc, I think make some sense at a full production level when you might care about ownership / copies / allocations, and want them to be explicit, but when you're just prototyping stuff to work out data structures and relationships, it's increadibly annoying IMO when you're refactoring.
Worth the read if you care at all for details in relation to green technologies.

> In his 1969 book about the early days of the helium industry, Mines employee Clifford Stebel admits that the hydrogen should not have exploded in this scenario, and hints that he tampered with it

> These airships could be immediately useful to the hydrogen industry, too; H2 Clipper says that if you're looking to export liquid hydrogen internationally, as many countries are hoping to do in bulk, its airships will beat rail, trucks, ships and even pipelines on price over distances greater than 1,000 miles – while delivering the H2 quickly to just about anywhere on Earth.

Much more interesting than the snarky question, Green yes, but what color is hydrogen when it burns?

Perhaps the next big scientific apparatus which needs to be moved, can be moved by airship? The article highlights advantages of avoiding cross-modal transfers.
I’ve had similar experiences occasionally with a few tech recruiters (this is an outlier experience not the general one). Incessant emails until finally one with something cute and a gentle note that they won’t bother me anymore. It’s really annoying because I feel cruel for ignoring their emails but it’s not like it’s going to change my mind. If your email got ignored just move on, but I do understand that the business incentivizes that behavior.
It handles the insanely tedious parts of package management like version mismatch.
If you want to hack, you should be able to connect to the i2c directly on the monitor end.
> The only value I have ever seen is "0x40". (The iDOT chunk contains 28 bytes, and this value is 0x28 in hex. So maybe this is related?)

This is backwards, I guess? 0x40 is clearly not 0x28; nor is 28 0x28; but 0x28 is 40 (decimal).
Presumably you would go ask Oracle, and then patch it when they provide a patch.
I think that I largely agree with you. Certainly a small number of determined and talented people can do a lot and can often move a lot faster than larger teams. I just wanted to temper the expectations that we'll get fully working graphics drivers in a year or two :)

Indeed RADV is a good comparison, though it bears notice that the open-source existing AMD drivers probably also helped a fair bit! That being said, there seems to be 3 people but maybe only 2, and the RADV project has been going on for around three years now, though there are a lot of contributions from outside of Valve.

RADV compiles Vulkan to NIR, so there is also the backend that compiles NIR to assembly that needs to be performant.

Though perhaps the Asahi Linux team can leverage a lot of work done by RADV for their platform, which could speed things up a lot!
An experimental collection of generic data structures written in Go
Genius. I keep declining it out of some misplaced sense of morality.
If you put the (unsigned) public key in the DNS, then a web client's DNS can be compromised to impersonate your site.

If you get the LetsEncrypt cert, then specifically LetsEncrypt's DNS client bot has to be compromised. Furthermore, it's not as easy as spoofing DNS; you also have to somehow obtain the matching token from the LE client<->server exchange.

Arguably, this is a tradeoff, rather than one being absolutely more secure than the other. The LE is one high value target that could be compromised once affecting many people.

In practice, it's the second one that's more secure.

DNSSEC+DANE really does beat LE securitywise, but then DNSSEC usually works over some non-automated registrar web admin panel.
The `nrf-rs` HAL is quite good, but there are a few differences in my fork:

- Replaced GPIO module with one with a cleaner API. Adjusted other modules to reflect this.
- Replaced timer module; original was a thin wrap of the PAC
- Tweaks to the RTC API to make it easier to set the timeout.
- Overall, brought the API to parity with the STM32 HAL I wrote. This makes code more portable between projects for me.
- Support for nRF-53

There were enough opinionated API changes that it would never get merged upstream in a PR.
Remix uses React. SvelteKit uses, well, Svelte. Both have been designed to adapt to any hosting platform, whether it's serverless or Edge optimized, or a regular Node.js server.
Oh yea absolutely. A lot of these things you describe have direct consequences that affect us today. I guess I was mistaken by using the word 'all' as we are still fighting for this cause today.
It would be really nice if the files were served from the root. IDK exactly how that could be implemented. Maybe put the UI under an "unlikely" url. But then once you upload a lot of people will have a hard time finding the UI again to change the contents.
Eric Clapton sued a woman who listed CD on eBay for $11. She now owes thousands
For me Veritasium lost all his credibility capital by the way he responded to Tom Nicholas’ video about YouTube sponsorships using Veritasium as a case study[1]. In stead of approaching the debate calmly (or better yet, simply ignoring it) he came to the comment section way too defensive, like a lot, basically calling Tom a lair and a bad actor.

Actually that is not quite true, Veritasium lost a bunch of his credibility capital when he made the sponsored content for the self driving cars. I never watched that video as I spotted it was basically and ad and was reluctant to watch his new stuff after that (though I did).

1: https://www.youtube.com/watch?v=CM0aohBfUTc
Selective Metals separation, may help alleviate critical shortages
I'm writing this from memory, with checking any sources. IIRC:

Designs like JNDI were widespread in the IT software industry at the time.

The academic prototype for all this was CORBA, the Common Object Request Broker Architecture. An object-oriented was to transmit data between systems running on separate processes, CPUs, remote servers.

CORBA was a next-gen RPC (Remote Procedure Call) framework, the data format on the wire closely follows the format for C structs using Sun-RPC, but was way better because these CORBA things were discoverable and described at run-time, rather than compile-time libraries.

That's right: RPC was initially a Sun UNIX thing.

Microsoft needed a way to do this, so they had COM, the Component Object Model, for run-time discovery and linking (late binding).. Microsoft got COM to reach across network connections, "DCOM", for Distributed systems.

Meanwhile, corporate IT was still pulling text out of databases and shoving it into C structs. It sucked.

Microsoft's object model was better, and Java was better than better, because you didn't have to license it to use it. Well, you did; it was like an MIT License.

Reason why IBM writes huge Java systems. And why Oracle owns Java. For some value of ownership.

Yay objects!
It would be simpler, much cheaper, and more transparent to use a formula. But that wouldn't allow the continuous charade of banker bailouts and unlimited federal government spending.
There was a recent 0 day in iMessage relating to image parsing, in a open library that Apple used. I’m not sure why the poster is being so vague, but the blog post is an interesting read.

The second comment just seems like a dig at apple in general.
If you really want to get deep into the topic of wood choice for self-bows, The Traditional Bowyer's Bible series is a classic.
Pre-generic Java required (un)boxing and runtime casts everywhere, so it wasn’t really safer than a dynamic language, just far more tedious. I’m thankful that we pretty much burned that code to the ground and started over. Those casts are still in the bytecode for the verifier, but at least we no longer have to reread them, and we have warnings when we violate the assurances that they won’t fail.
I'm surprised too; in the Windows world, two decades ago, "skins" were popular and those essentially turned every single UI element into a bitmap. On the hardware of that time, their impact on performance was pretty minimal.

Of course, "every UI element is a bitmap" is not a good idea anyway, for other reasons, but seems to have someone become the norm for web and mobile.
Won’t this have a painfully long delay as the monitor negotiates the different input port?

Not only does every monitor I’ve owned take seconds to do this, it often screws with the desktop layout and such when display devices seemingly come and go. Or am I misunderstanding this?
https://github.com/Music-and-Culture-Technology-Lab/omnizart
Wait, you're complaining that the people who used Rust to write a production software enjoyed it so much that they want that experience for all other softwares too? They enjoyed it so much that they told others? and others who also enjoy writing code in this language want to work for you? Are you saying you're afraid that "too much of a good thing" could cause issues for you?