skysight-inc/HackerNews huggingface dataset:
First of all, disagreeing with someone's assessment of learning difficulty isn't something that should deserve downvotes at all.

And then I've been working in Rust with beginner and mentoring them while they learned Rust, and I can assure you that the difficult part that most people struggle with is just half a days of learning actually[1]. Then you put in practice with exercises, to familiarize yourself with the syntax and the std lib, for a few days and you're ready to code.

The difficulty is to overcome the first step of assimilating concepts, that you need to unlock the next steps. If you skip the concept phase, then you can remain confused for a while I guess.

[1]: I've just check my slide deck, Ownership + Borrowing + Arc/Rc + RefCell/Mutex + Lifetimes + Send + Sync, the entire package of Rust hardcore concept that everybody struggles with, fits in 63 slides, with the exercises, and I usually cover it in half a day. And it's accessible to pretty much everyone without prior Rust or C++ experience. I even re-explain what a thread and what the heap are.
Think of it like a riot. What does smashing windows have to do with anything? Yet one follows the other.
Thanks! I bought it like a month ago! Haven't had time to use it much, but it came handy to downgrade my reMarkable 2 :)
https://archive.ph/gbGxj
Woah, really? Would love to hear more. Do you have any blog posts or anything about this?
Japan also had no economic growth and had a population decline over the past couple of decades - this for sure must cool the housing market.
Where are the designers? Expected some novel UX that I never considered to emerge but really hasn't outside the ubiquitous movement in games where you point an arcing arrow to move. Apple's gaze and pinch is sort of thing I expected more of from normal, non-giant-company designers.

Yes, for the most part VR gaming is awful. Sometimes in a kinda fun way. I wonder if we'll look back with nostalgia on some of these weak games like we do with weird old turbografx platformers.
The camps rhetoric is new. If anything that's further evidence that it's caused by the times rather than the personalities.
Retailers also seem to be deploying a solution that includes moving their stores out of cities that don't crack down on theft.
I think recursion is incredibly intuitive if you just start with an obviously recursive data structure. Give someone a tree, and writing a recursive function is a very natural thing to do.
FCC Reinstates Net Neutrality
Was that the hardware/software used in the Voyagers?

That seems too 'heavy' for use in a bare-bones environment like space-craft.
Are you saying durability is "orthogonal" in that it should be managed outside of the database (in your example, perhaps by copying sqlite files to durable storage)?

If not, then your proposed design seems pretty different from MemoryDB; yours doesn't persist data in the event of machine loss or reboot.
Tell me you've never started an assignment the day before it's due.
LeifCarrotson was arguing that, but mistakenly typed out about 10 words that would indicate the opposite
Testing if somebody groks recursion or pointers is the easiest litmus test to see if somebody "groks" programming. They're not "easy" concepts, and usually people have had to break through a wall for it to be comfortable with them. They make great interview questions, doesn't need to be long or complex problem, just has to have either pointers or recursion in it.
I'm amazed that all of these VR players are dropping the world's easiest to hold ball.

Just give people a damn VR headset with the same compute flexibility as a Windows, macOS, or Linux desktop and do away with these stupid walled gardens.

The units would fly off the shelf because, whoa! You could actually do something with the damn devices.
It looks like scheme.

Anyway, that unindented code hurts my eyes. (It's not as bad as an unmatched parenthesis, but it's close.)
Canola: CANadian Oil Low Acid
How big is it really? They’re firmly dominated by state politics which is going to be a big deal for a lot of people and they’re hardly immune to the weather, power, etc. problems.
I feel sorry for any jury who has to keep track of 86 counts. The Ross Ulbricht and SBF trials look simple by comparison.
There are quite a few unattended stations in NZ
Math background here too. Long before I first sat down at a computer (in 1981), we learned about the inductive principle in math class, and did some proofs with it. Later on, our introduction to recursion (in Pascal) started with a review of induction.

Of course the next phase is trying to do everything with recursion.
I genuinely wanted to. It was just too bad to be useable.
This is Polish notation [1], which puts a symbol for the function at the front of a term and the arguments of that function after it. So (* 2 3) is what you'd usually write as 2*3.

So you can read this code:

(define (expt n p)
(if (equals? p 1)
n
(* n (expt n (- p 1)))

As this more typical psuedocode

function expt(n,p):
if p = 1:
return n
return n * exp(n, p-1)

Or the more mathematical framing:

n^p = n * n^(p-1)

[1] https://en.wikipedia.org/wiki/Polish_notation
Indeed - https://en.wikipedia.org/wiki/FBI%E2%80%93King_suicide_lette...
No Tenstorrent wouldn't have any advantage in choosing x86. My argument is that Intel as an organization would still face the same institutional inertia if they developed a RISC-V cpu as they do with their x86 cpus.

> that said, I believe a cleanroom RISC-V design by Intel would still progress faster at Intel than x86

Possibly. But it would still take a lot longer than Tenstorrent or even AMD (should they decide to do this). There's a lot of tasks that Intel tends to throw bodies at that an AMD or Tenstorrent have automated.
Oh god. The blind faith in reductive, objectivist, rationalist meritocracy that somehow "everything can be measured perfectly" and "whatever happens is completely unbiased as proscribed by a black-and-white, mechanical formula". No, sorry, that's insufficiently holistic in accounting for intangibles and supportive effort, and more of a throwback ideology that should've died in the 1920's. Some degree of discretion is needed because there is no shortcut to "measuring" performance.
US economic growth slows but inflation grows
Yeah this is a really weird shift that has happened in a relatively short time. In Sweden we have strange groups of nazis and hippies that you wouldn’t have thought would happen in a million years when I was a kid in the 80s/90s.
The stack pointer is as much mutable state as the loop index.
Yes, but induction and recursion are essentially the same thing. If you understand one, the other is pretty obvious.
Yes that's my take too. Once you know something well, it's easy to formulate it elegantly to say it's nothing more than the monoid in the category of endofunctors or whatever, but how something is conceptualized by those who get it has no bearing on how it's learned. A lot of the time, it seems like lots of worked examples without any theory is the way to go until something clicks.

All that said, I can't understand why someone would find recursion complicated which probably means I'm unsuitable to teach it.
The ambitions of China's BYD stretch well beyond electric vehicles
Just curious, do you also really dislike when Wendy's social media account cracks jokes about other fast food chains?
And how is it money laundering if it turned out the money wasn't proceeds of crime.
I second this. Though I might just (heh) be too biased having today added some common Just recipes as global shell aliases [1]

I also use Just for build and deploy commands. Other thing I was thinking of was setting environment variables. Complex pipelines can be split into several dependent recipes. Or using shell aliases you can string them together yourself with regular pipes in very compact form. Just recipes defer to shell or a programming language of your choice. Just makes some shell stuff easier without replacing or hiding it.

[1] https://just.systems/man/en/chapter_68.html

Edit: I also added Atuin https://atuin.sh/ recently to better deal with shell command history. Though that one I’m still learning.
honestly, I see this as a sign of Google bureaucracy/cost-cutting taking over the company's culture. Considering how much innovation in tech is happening right now, blowing cash on a dividend rather than internal projects that could make big returns seems like its completed its journey to becoming the next IBM
About 25% of Americans age 50 and older expect to never retire, AARP study finds
Interesting. I about I found the game boring
That may be true, but most aspects of hardware exist just below a very exciting threshold right now.

* The resolution in commodity headsets is just low enough that text is barely legible. Productivity apps become suddenly practical when you can render good-looking text.

* It's been years since the announcement of holographic lenses, which will remove the headache-inducing fixed-focal-length and pupil misalignment; significantly reduce headset size/weight; and increase the brightness and color gamut, and make the headset cooler, because the display backlights are replaced with lasers.

Most of the tech stack for SteamVR just needs to be semantically moved from "game engine library" to "HID & UI/UX framework".
Because Ruby and especially RoR is a strict downgrade in every dimension compared to .NET. Now, these developers could have been using old .NET Framework, in which case we usually pretend they don’t exist because it’s like stubborn Python 2 of .NET that is otherwise the most productive platform for back-end (with really, really good performance).
Borges's short stories are almost perfect nuggets for computer scientists, seemingly covering such topics as recursion (Garden of Forking Paths), the consequences of infinite memory (Funes), complexity theory (Library of Babel), virtualization (Tlön, Uqbar, Orbis Tertius), and so on.
https://archive.ph/2hBGV
But you don't need to "walk through" recursion, you just need to assume the sub-calls do the correct thing. That's the magic of it -- like induction in proofs, if you convince yourself that the function does the correct thing if all of its self-calls do the correct thing, then your function is totally correct.
Wonderful! Want to buy a package of razorblades? It's time to get your retinas scanned.

Absolutely revolting that any retailer would even consider doing something like this.
I recall reading or hearing that a bunch of senior GOP leadership got together immediately after Barack Obama’s election and agreed explicitly that their approach was going to be obstruction.

And that worked, but then the next generation of elected party members seemed to be obstructionist only. So much so that in 2017 when they held the executive branch and both houses of congress, they couldn’t get anything done.

We’re all sleeping in that bed that they made.
As someone well into middle age, I hoped that there would be more insight in this article than there is. The author makes some assertions that there are unrecoverable mistakes one can make, but doesn't really support those assertions in any way. I would like to know how the author would respond to any assertion that he is simply wrong, but from the text I have no idea.

For my own part, I feel that the picture painted in the essay is too bleak. Of course there are some unrecoverable mistakes one can make, but really not that many. We are each born into a situation that is the result of decisions made by others over which we have no control, and we have to play the cards we've been dealt and try to make some joy out of what we've got. Later in life, the cards are dealt to us by younger, less experienced versions of ourselves, and we still have to play those cards and try to make what we can of it.

On top of that, the theme of the article seems to be that life is a minefield that one should proceed through with extreme caution, less you fuck everything up with one misstep. But adopting that worldview is itself a choice, and one I think that is more likely to lead to unhappiness than taking a moderate amount of risk.
Maybe, but not necessarily. It really depends on what they actually believe (or say they believe) specifically. If their belief is "societies work better when governments don't interfere with markets", then their beliefs say nothing about what individual people should do in situations where a government does interfere with markets. They may also believe that if you can't fix something, taking advantage of it is justified, in which case they are not being hypocritical. That's not to say you can't regard such a position as unethical. However, I think many if not most people use systems they are in favor of dismantling. For example, people who believe housing is a human right don't typically donate their houses when they move, they sell them on the open market.
Wok hei isn't a home cook technique
Pointers aren't hard, the languages used by most intro to CS classes are the hard part. I taught myself z80 assembly in middle school and didn't learn until years later that pointers are supposedly hard. From the direction I learned it, you address memory with numbers, and obviously you can do arithmetic on numbers. This is one of the simplest things in CS to learn. It's the * and & soup that becomes a nightmare to beginners.

Lest you think I'm just a bragard, I never managed to get better than a C in any calculus course.
I have more fundamental concerns to talk with a theoretical physicist about first :D

Time to kick an ants nest here...

Quantum mechanics is a useless study that had no business being a scientific field. The most fundamental principles, like quantum superposition, can never be tested or validated and therefore could never be used to be predictive of anything other than similarly theoretical ideas.
Neither in San Francisco.

In 2005 Google wanted to do a nice gesture and offer free wifi across SF. The Board of Supervisors literally asked Google how much they were intending to pay the city in order to offer free wifi... SMH.

It of course never happened.
Pointers are so easy to work with that they're still the cause of major security flaws and crashing programs every single day.

The concept of pointers isn't too hard if you know how memory works, but that hasn't made working with pointers any easier. Any serious work with pointers quickly devolves into questions about ownership, lifetimes, and figuring out the proper sizes. Plus, many educators seem to skip verifying that students actually know how memory works before introducing pointers, which leads some students to believe that pointers are some kind of language feature rather than a core concept of modern computer hardware.
It's a detail, but I disagree with the fact that looking at who is worrying is not a good element to evaluate if the problem in question has legitimate arguments to generate worry. If someone usually optimistic is worried about the subject X, it is a good indication that this subject X has good arguments, as it has convinced the optimistic person. If the subject Y is a worry only for the "worriers", then it is a good indication that this subject Y does not have good arguments, as it failed to convinced people who are more difficult to get worried.

(and, sure, one can talk about "are people informed" or whatever, but this is a second order effect and is just a slightly disguised they-disagree-because-i-am-a-misunderstood-genius fallacy)

For the AI subject: you cannot put in the same bulk people who worries that AI will be used tomorrow for bad things and people who worries that AI will become intelligent and be a threat for humanity, because those are two things very different with very different consequences. What you need to do in case of worry of bad usage of AI is very different of what you need to do in case of threat for humanity, sometimes opposed (bad usage is about putting rules and fair access, while threat for humanity is about forbidding or controlling fundamental research).

It's a bit like if in a parallel universe, someone says "people are worried about immigration. Sure, some people are worried that migrants are invading us, and others that migrants are being treated unfairly. But they are worried, so it is the proof that worrying about immigration is legitimate, and any criticism about these worries are just people who cannot have a logical argument".

For example, I don't think people who are worried that AI can have a bad usage and that we should be careful about that are feeling attacked by the "coffeepocalypse" argument. People that are worried about a bad usage of AI are not worried about AI itself, they are worried about a bad usage of technology in general, and it includes thousands of things that don't even involved LLM or recent development in AI. I think it is more directed at the lesswrong-pseudo-intellectuals who think they are deep and smarter than everyone else when they are just playing around with basic concepts and misguided ego trip.
In my experience, Go appears simple as long as you’re solving simple tasks. Once you need to model fairly complex semantics, whose structure and detail depend on your business domain, Go code turns illegible, with lots of hackily lumped together bloated nonsensical channels and for-selects stemming from async IO and multi-threading forced into the goroutines syntax, with hard to formulate structured concurrency. And then you bolt on your validation logic on top of it, with several Go idiosyncrasies, and then you need to explain the distinct consumer-side interfaces, underwhelming generics and myriads of conventions based rules. One could claim that’s not how one writes “good” Go code. But that’s what depends on the complexity and dynamism of your domain logic and the folks you work with. After Java, production grade Go for larger projects is terrible. Null pointer method receivers, interface reification. And now the experiment with the functorial ranges, increasingly with more and more genetics, all without any syntactic sugar… hard to read, hard to explain.
Oh and the GC is rather inefficient compared to most JDK distributions. Compared to modern Java or Kotlin, for my project requirements, I don’t want to do as much Go as I used to. JDK Mission Control and Flight Recorder alone with great IDEs and profilers are golden. And you pay in RAM for JDK apps.

As for Rust, it just requires more upfront cost, but makes you consider potential failures at every step. Debugging production code isn’t fun, fuzz tests aren’t enough to assure quality to the extent Rust’s type system can. I trust rustc much more than I trust myself or other devs. If the code passes rustc, and the type semantics are correct, I’m 3/4 certain the code is correct, that’s a very high watermark, albeit at the cost of the upfront effort to satisfy the type constraints. Much more efficient in terms of dev time than debugging Python or Go at runtime.

Anyway, one can easily run many Python packages on GraalVM Truffle for direct interfacing with Java, Ruby, R, and via PyO3 with Rust, for which you have the native Polars data frame library, which all cover a good chunk of Python programs. Rust also teaches one to do proper ownership accounting for the variable bindings, great for C++ devs and for heap escape analysis by inspection for Go devs alike. Lots of Go bugs result from lack of understanding of ownership and implicit reference binding as opposed to copy and move semantics. Some of that was now “improved” with Go 1.22 for closures in loops.
Or Ebox. In fact some of hurdles were documented on dslreports forum. Starting with wholesale access to cable ( worked OK for a while ) continuing with wholesale access to fiber ( never happens ) and ending with the end of the 'sane' rates for cable ( final nail before Ebox, Destributel and other were sold to Bell/Telus/Cogeco )
> Depends on what your philosophy is. You believe in the software commons and the free sharing of software? You would want software to remain as a public good so no one can profit from it exclusively.

> Are you a business who made some software? You don't want others to resell it because it's your work, you made it and you don't want others to freeload.

I cant help but notice that you assume everyone uses money as a measure of desirable/undesirable outcomes. Whenever I publish a library/project with a GPL license (my preferred license), it's so that others can use it. I have a well paying job that's enabled in part by others sharing their work[1], so I let the "freeloaders" have at it - I too am one, after all.

At the time I release the software, my problem is adequately solved: I already did the work , maybe someone else may benefit. Creating/sharing value with others is the point - I don't mind if someone else sells it : if they abide by the license, that means I can sell something identical for half of whatever they sold it for if I suddenly felt competitive.

1. I'm amazed that I can use Linux, git, hypervisors, orchestrators, various computers and interpreter, libraries, ops tools and more all for free,and with the ability to pry them open and make any changes I want! How frigging cool is that?! I'm compelled to pay it forward in any way I can.
> If Congress wants to override this rule, they can hold a vote and do it tomorrow.

As elsewhere in the thread, I find this point mostly theoretical.

You could say with an equally straight face that Congress could balance the budget any old time it wants to.

You could also point to some quantum mechanical statistical possibility of a fored bullet passing through its target.

There will be no improvement in the collapsed political situation before us until we get past discussing hypotheticals and set about reform.
I find CNC is a time-saver for one-offs when the work is complex enough that it'd be difficult-to-impossible to do by hand, eg complex curving cuts, engraving/pockets, etc.

I actually saw an unusually straightforward example of this last year - a group of friends and I were making instances of Tyler Gibson's 1-sheet portable bike rack design (it's great, check it out: https://www.thetylergibson.com/building-a-better-portable-bi... )

One group of two-ish people used jigsaws to manually cut the pieces, and I used a Shopbot 4'x8' CNC router. Very roughly, it took about twice as many man-hours to make one by hand, vs by CNC, and the result was less clean. CNC could have done even better, but due to warping of the sheet, it failed to cut all the way through in places, and I had to do a cleanup pass with the jigsaw. And once the upfront cost of generating the toolpaths etc was paid, it would improve again.
Rapeseed oil for cooking is a staple in Germany.
If erucic acid or its thermal products are the cause, there would also be many cases of lung cancer in Germany.
There is some truth to this. Imho the next level of htmx is unlocked when you componentize everything like a React app...but with nested routes corresponding to nested components like a Remix app...and using an HTML generation DSL embedded directly in your language, so HTML becomes a first-class citizen of your language's constructs, rather than a templated afterthought. I have a demo of this: https://github.com/yawaramin/dream-html/tree/todoapp/app
I’ve used this https://github.com/secretGeek/ok-bash

It is a menu that works off a file that contains a collection of single line commands.

I like it because it is a local command that is only relevant to the project I’m working on, and sometimes after months of absence it is easy to pick up where I left off.