skysight-inc/HackerNews huggingface dataset:
This article is aimed towards students. It's great advice for students who are in college, know very little, and want to improve their CS skills.

It's poor advice for someone who already has a STEM degree and wants to build something useful and profitable. If you already know how these things work, your time is better spent on the "edge of the circle": http://matt.might.net/articles/phd-school-in-pictures/ which applies to businesses and startups as well.

If you're in the latter group -- you've already got the skills to build real shit. Don't waste your time on homework problems. Find a problem you have and build a solution for it. Don't listen to people who tell you to work on homework problems that have already been solved; it's a complete waste of your time if you already know the fundamentals.

As for stock trading bots -- if you don't have a mathematics degree or equivalent (e.g. having incredible math skills), don't even bother. You won't be profitable, and you will learn nothing useful in the process, because you will approach the problem as a naive CS student would. Smarter people than you have made trading bots and have failed miserably. Without having an extremely strong foundation in mathematics, your trading bot will amount to nothing more than a futile exercise in gluing APIs together.
Perhaps part of a new breed of middle class. Instead of a distance or management friction, this is a scaling friction. In order to scale, programmers are required. Maybe this correlates with doctors and lawyers, albeit a different friction, one of artificial scarcity (limits to who can attend medical/law school, and whatever certification is required afterwards).
As I replied on another thread, I don't do containers and this laptop is doing just fine with 8GB, running stuff like W10 Pro and VS 2019.
I did not know that one can settle a pyramid scheme in US. Good to know.
If you could make them think about and want to work in your factory the way they think about and want sex, you'd have a full roster every shift and would be turning people away. Such an oversupply would naturally see the value of that labor drop to near nothing.
Alistarh et al. (https://arxiv.org/abs/1311.3200) show that assuming we have a kinder, non-malicious scheduler, the situation looks even better: lock-free (some process can make progress) algorithms have a stronger progress property of being wait-free (every process can make progress).

As omazurov mentioned as a top-level comment, threads can also die, which is rather like never being scheduled. In practice, I suspect that you're right that it's often too extreme of a model—many programs use locks and don't worry too much about this issue.
State pension won't be nearly enough to cover your living standards. You'd still pay insurance (less than before retirement though) and taxes off your pension. You still have to save on your own or go with an additional private pension scheme in Germany to somewhat be able to keep same living standards.
I ran into a bug with GTK2 stalling out with some malformed DBUS messages (symptom: your application takes an additional 20 seconds to start). So I made a sample app that demonstrated the problem, ran some system traces, tried to engage the GTK developer community and only got an "eww, gross, not touching that".

It's pretty clear that GTK2 has been left out to bit rot at this point and it's going to completely collapse at some point. Only option is to update your old apps.
Indeed, a cool cameo. She was one of the designers for the "Acorn RISC Machine" (today known as the ARM architecture).
It's the original Dutch word for "quack" anyway, fully "kwakzalver".
What do you use mruby for? Is the use case purely for embedded systems?
or just boot usb :)
Kind of like a red team.
At 3x memory you still get comparable performance, and memory is fairly cheap. In particular, memory sizes continue to scale, unlike CPU speeds, making GC an increasingly favourable proposition.
What a beautiful story! I've read a similarly impressive account, where a GNU/Linux system was revived in comparably wizard-like manner, with Kernel hacker Al Viro involved: https://yarchive.net/comp/linux/extreme_system_recovery.html

It was linked to in an LWN article's comment section, titled "If you think you're really good, read this.", or something. The story proved very effective at humbling its reader for me.

That doesn't change the fact that I, too, once felt like the uncrowned teenage king of emergency system rescue operations back in 2002 or so, right in my parents' basement. I had started recursively deleting / by accident, and ended up with most directories, /bin and /sbin included, already turned to dust, and most of my as of then proudest achievement - a Gentoo Linux stage 1 installation - gone.

I dug myself (and the standing remains of my /home) out of that particular hole by virtue of still having an instance of a browser (I think firefox) running. Mildly panicking, I still left everything untouched ... and after a few hours of thinking hard about what to do, I arrived at the following: I set up a webserver on my mom's windows PC with am embedded PHP interpreter, and hacked up a script that enabled file uploads via HTTP over the LAN. After using that from within my still-running browser (fortunately, it could still list the contents of my home directory) to evac the most precious artifacts my ~ had in store, I rebooted my machine into the lightless nothingness of not having a kernel image in /boot any more. Another few hours later, I had Gentoo reinstalled, and copied the rescued files over to my own machine again - and felt like I had levelled up a little bit.
You are describing the elements of most of the best ideas in history.
A load pair takes one address generation and one slot in the load queue but returns 2 x 64-bit. It doubles your load throughput at the cost of the complications from an instructions that return two results.

Apple's A14 can issues three loads per cycle. Assuming they can all be load pairs (I don't know currently) that would be 6 loads per cycle. This is frighting :)

The story is similar for store pairs, but probably less important as stores are rarely on the critical path.
I wish a couple of more Rust aficionados, and the Android Studio team, would do the same instead of using most likely beefy Ryzen desktops.
Newer concurrent java GCs (shenandoah, zgc) provide consistent ≤1ms pause times independent of heap size. That's a reasonable latency for most soft real-time tasks.
Quality > quantity.

Personally, I don't see the value in much fiction unless it is exceptional. Instead, I would prefer to read notable works of nonfiction as well as extremely controversial ones that influenced history.
I can imagine it leading to ossification of kernel internals.

Imagine when someone comes up with a revolutionary new paging method, but it causes everyone's eBPF scripts to fail to load and a bunch of tools to break...
Yaris GR
Well apparently their methods don't work very well.
When I first heard of Vitess I thought it was gonna solve a bunch of issues for our team.

But then as I started taking a closer look at it, I realized it was more likely to introduce a host of new, hidden issues, than really solve any of our problems, or make things simpler. For example, it doesn't magically give your cross-shard transactions. And there are situations where it can cause straight up deadlocks, if you're not careful about how you structure your queries.

So basically your devs can see the DB as "one gigantic instance"... but they also have to be (painfully) aware of what Vitess is doing under the covers to avoid poor interactions with it.

Doesn't sound like a win to me.
The line is blurry.

JIT compilation means compiling code on the fly right when you're about to execute it. When the code is part of a larger program, jitting allows to compile the parts of it you actually need and avoid wasting time to compile other parts. It also allows to compile the relevant code paths based on dynamic flow analysis, which often involves interpreting your program the first time you run it and emitting instructions for the next time around (tracing)

If the code unit is small and you know you're going to run it all, you can compile it in one swoop. If you compile it when you load it in the kernel, as opposed to compiling it lazily right before you run it the first time, i think it's fair to call this Ahead-of-Time compilation, even if the compilation happens right next the use site and not as part of the developer tool chain
See time table of your post, my comment and your post'comment and your answer to my comment.

You are too slow. Visit your pornhub by your self.
But it’s an article about AES, which is the block cipher. Block cipher modes are important to a larger solution built on AES, but they are orthogonal and not even specific to AES.
On day in my previous job our junior support guy started cursing loudly. He had done what he was asked for and did some some small, _almost_ day-to-day support request which was supposed to do some requested maintenance things for some credit card accounts our company was handling. He by some small accident ended up invalidating the cards with our CC operator and closing the accounts on our end.

He was so wrecked about it and we, the more senior guys started helping him and comforting him that "yeah, this kind of blunders can happen to anyone, no worries. Let's figure this out together.".

The other guys figured how to restore the data into correct setup on our end, and I found some unimplemented badly documented "undo invalidation" endpoint from the CC operator with which we could fix the stuff on the operators end.

So we spent nice and fun evening together figuring out the problem as a team, but damn the guy was so torn up about his small and completely understandable fumble that nobody else needed to critique him about it.

The funny thing is that with this kind of blunders one learns a lot more and a lot faster than usually. People need to make mistakes. It's usually the best way to learn.
My guess would be

> Seamless interop with React Native. Use core React Native components with Vue.js syntax out of the box
The problem is that to get the new features you have to accept a new way of working. One that is worse than the classic MacOS or Windows 2000 was. Another reason many folks are in no hurry.
My version is even shorter and has a closing <body>-tag and even <html>-tags for the swag:

<html><body><script src="https://cdn.example.com/js/todoapp.min.js"></script><script>new TodoApp({});</script></body></html>

It's obviously just a concept and doesn't work yet (example.com, durr!) but it's in the same spirit. It only relies on a general purpose todo app library. Default options of course! (Which fortunately make it mount on body)
I haven't even attempted to implement AArch64 and only browsed the ISA, but it's all of these things. Instructions are many and some semantics that are more painful, like handling flags which are exactly like mini registers and the load pair/store pair instructions I mentioned. Also, there are more addressing modes which puts pressure on the load path. All this complexity hurts even more when it comes to verification.
Which effectively translates to, "Stop resisting! Assimilate! Tell me how many lights you see!"

Some people here have yet to learn that HN is not a forum for free, open-minded discussion.
Anybody know what would stop home printers from printing like the way they printed the bot?

It really seems like a lot of prints of mine would be way stronger if it where done at a angle like that that.

note I 3d print everything all the time. My house is speckled with orange printed parts (I like to point out when something was 3d printed).
Windows does. MacOS does. Wake me up when wayland is stable. Maybe in 10 years?
Let's ask some questions first.

Are you willing to give up your cosy holiday plans?

Are you willing to give up your (at work) privacy?

Are you willing to work overtime without compensation or complains?

Are you willing to work for a company that might drop dead in 2 months?

For short: are you willing and able to take a risk? If yes, then it is not hard. But knowing my (Western European) colleagues, the most likely answer is no.

Do not underestimate the value of stability and predictability.
Problem with 3D printing is how slow it really is. I do see a path for better printing quality and overtime becoming indistinguishable from injection molding, but I do not see any path for beating a 15 second cycle time. Printing a coffee mug can take whopping 8 hours, depending on specifics of quality and the machine.

I feel like Injection Molding is far more amazing, interesting, intriguing and challenging process than 3D printing and yet, it gets zero media coverage. Before people respond to this - yes, I know the pros/cons of 3D printing and it certainly has place in manufacturing processes. Just pointing out the media hype around 3D printing which I thought would die down after 2015 or so... but it continues to overwhelm news sources.

Edit: Goddamn it HN, why are you all responding to the pros/cons of 3D printing? My complain is about media coverage and how click baity engagement metrics propelled 3D printing into this glorified do-all-world-changing-technology. It disproportionately gets attention, was just using injection-molding as a talking point. There are so many interesting manufacturing techniques. Every MBA exec wants their engineers to explore 3D-printing without knowing its downsides, thanks to the stupid media.
Windows phone's apps were built in C#, which arguably had also a deep pool of developers, and it didn't help. Visual Studio was also the arguably best IDE around at a time where XCode and Android's Eclipse plugin sucked hard, and still it mattered zilch. The real problem was market share and mind share, two factors in which Windows phone tanked bad.

For instance, Apple forced people to write iPhone apps in Objective-C for years and nobody avoided the platform because of that, even buying Macs and paying 99 dollars a year for the privilege of writing and selling iOS apps.
There have been other images since that suggests a certain percentage of the London population decided to leave.
I use zsh for interactive shells and bash for scripts.
I don‘t think this tutorials aim is to use this implementation in production. I can understand the security risks but it‘s easier to understand and maybe improve a technology when one takes it apart first.
1. European-style folders with elastic bands at the open corners (http://www.ldapapeterie.fr/chemise-elast-24x32-cl-5-10e-asso...)

2. 8oz Rip Its

3. Toyota Hilux

4. Small but rugged SUVs (RAV4 Adventure and maybe Jeep Cherokee are the only things even close in the U.S.)

5. Tim Tams. They haven't been available since COVID.
Standard Disclaimer: This is from my own personal experience. YMMV.

This looks like the same type of Gold Rush that happened 20 years ago in the dot.com boom/bust. Same advice I learned the hard way applies today as I wish I'd learned it then - "when there's a gold rush, go sell shovels." Or in this case, as a technologist, sell topographical survey info you've collected, gold panning tutorials, fully outfitted claim excursions (you get the idea) - ANY knowledge you have about HOW to do what people THINK they need to do to find gold. Don't take equity, take cash today. It doesn't matter if they get rich or not, YOU make sure you get paid FIRST and be clear that if they don't want to pay for your services, their competitors certainly will.

To continue to abuse the analogy, to the business person we technologists are now and have always been "resources" to be used as a means to an end. You think they want to give their "pack mules and shovels" a cut of the gold? Unless you have some business domain knowledge, you'll never get an equal seat at the table. 9 times out of 10, if you DO have some business knowledge, you can probably make more money by going off to become a direct competitor. Or, better yet, gain some knowledge of the field and work with a competitor who has a better vision.

I've been inside 4 start-ups in various stages, and one post-IPO company that included stock options over the past 20 years. Only the dot.com era company ever amounted to anything, and that was dumb luck WRT having an IPO when people would force money on you for doing eAnything(TM).

I follow one primary rule when taking a job: you're either there to earn, or you're there to learn. It you're humble enough and not an idiot, you realize that there's a number of things to "learn" at any point in your career between different industries, different career paths, and different levels of position. If you think you're "too good" to do some job, you may be right but you may also just be an asshole.
Care to elaborate? There are some nifty tricks when it comes to golfing JS.
Same situation here, it is easy to just hate Elop given the M$ hate, when in fact this was mostly pushed by the Nokia board members themselves.
For anyone else unfamiliar: "a calibration and torture-test part for 3D printers." http://www.3dbenchy.com/

It is shaped like a boat.
Tesla could open a factory in Thailand the get rid of Thailand's import tariffs, and perhaps this would also make export to other SEA countries easier and cheaper [0].

Anyways ... do you believe Tesla will be gone in the future or do you believe the stock price is unjustified and should be a bit lower? Personally I think Tesla is here to stay and perhaps Elon can expand the company into different markets and that could increase the value of the company. If the stock price drops a bit, that I think is fine.

---

[0]: https://en.wikipedia.org/wiki/Automotive_industry_in_Thailan...
why not, that's only one direct step removed from thinking that conformity to popular beliefs is cool.
Wow, wow, easy, gentle man...
Except that Symbian developers had just been asked to move into Qt and PIPS the year before.
Yep. Currently Android 0day is more expensive than iOS.

https://zerodium.com/program.html
?

Lots of things don't work in d's CTFE.

It's certainly very useful, and much better than e.g. c++ constexpr. But it's still worlds away from proper lisp metaprogramming.
I remember it getting popular years before macOS switched. I believe Oh My Zsh (a zsh framework) being popular when I first tested it out and that looks to be 10 years old.

The things that got me to try it was being mostly compatible with Bash and having a lot of features that Bash only got later. I remember liking recursive globs, which look like they got added to Bash 4, but my OS may not have had it at the time.
Through 10.2.x it was tcsh, then switching to bash in 10.3? I think?
> Surely there's something in-between. Say, perhaps, black people make you uncomfortable, such that you're inclined against hiring them and you preferentially hire whites instead. Then, you wouldn't knowingly possess a racist motive but would be definitely acting racist and perpetuating racism.

That seems pretty clearly to be a racist motive. "Black people make you uncomfortable" is literally traditional racism, and action taken based on that motive is racist. Doing something like that without thinking through your intentions too hard doesn't make the act unintentional, because the intent is there whether you consciously evaluate it or not, and it doesn't change the motive. That person wants to be racist, and then directly is.

Someone who buys a chicken sandwich only because they want a chicken sandwich has no such motive or intent.
GNOME and KDE are not the only desktop environments on Linux [1]. MATE forked from Gnome 2, much closer than KDE yet they are separate projects. Trinity forked from KDE 3, XFCE is a GTK based project.

Imagine same argument for macOS and Windows (if that was possible) — lets merge UI. It would be complete disaster, hated by both camps.

[1] https://wiki.archlinux.org/index.php/desktop_environment
Or you know, the general decline of desktops from "the only computing" to "secondary computing after mobile".
The reality is that stock market trading is like a normal business selling products except you provide liquidity instead of products. Now imagine the market you have chosen needs 1000 widgets per day. If there are competing factories in the market place that already produce 1000 widgets then your only chance of breaking into that industry is by displacing existing competitors. You need to have a better product (or what the finance guys call an "edge"). The vast majority of people don't have such a product idea. They would probably just produce the same stuff the big guys have been making and then wonder why it isn't making them a profit. The market is already saturated with those widgets and there is no need for more factories.

Replace widget with liquidity and factories with traders and you should immediately see why most traders are losing money. They are operating in markets where their liquidity simply isn't needed.

If you want to make money off of trading then you have to find a market with low liquidity where having more traders is actually welcome but why do hard work if you can just invest your money and still get good gains without working?
And yet the Iran deal is gone and not coming back, and recently the US has pushed Arab states to normalize relations with Israel.
Yes, and sea level is driven by changes thousands of miles further, including ice volume at the polar caps, undersea currents, lunar gravitational pull, etc. 130 miles, when we're talking about sea level, is nothing. And these trends are true across the globe. Sea level has only been rising at the rate of 1 foot per century. And that rate has been pretty steady for thousands of years (it didn't start at the beginning of the industrial era).
Vaccine Safety to Remain Unclear Until Millions Get Their Shots
Māori is on a really interesting trajectory in New Zealand. There was a huge decline in the 1900-1960 era, where kids would be punished at school for speaking Te Reo (the Māori language). It was headed towards being a dead language. There were then huge efforts by Iwi to promote and normalise Te Reo, through education and media such as Māori radio and TV.

Over the last decade or so, though, I feel there’s been a cultural shift in New Zealand where Te Reo is being embraced by New Zealanders in a new way: Māori words are being incorporated into our English dialect: “Do the Mahi (work)!” someone might say, or “let’s have a hui (get-together/meeting)”. It is also regularly spoken by news anchors on TV and Radio, e.g https://m.youtube.com/watch?v=U_CpvfR2WkU

It feels new and globally unusual. It almost feels like the first inklings of a new language - an English/Māori creole of sorts?
Or even easier, in the process manager. Just right click -> Go to Service.
Former Nokia employee, I had two Lumias, still use my 650 as travel phone.

On its heyday (approaching 10% in Europe), Windows Phones were seen as the alternative for those that wanted an Android alternative and didn't care about iPhone.
Learning to Focus Your Developer Brain
>I warn you though, this is a controversial subject because of some of its possible implications.

This is a really sad state of science we are living through.
I'm aware of this (I've been doing since RISC-V before it was public), but it seems unlikely to me, knowing how these companies operate, that Apple would use RISC-V for anything when they already have extensive HW and SW Arm64 IP, expertise, and infrastructure.

NVIDIA's use of RISC-V is for the internal power sequencing cores and similar tasks. This is not going into the shaders, nor is Arm64. Their future use of RISC-V for stuff like this will probably continue, but it seems unlikely that they will ever release anything with a user-visible ISA based on RISC-V.