skysight-inc/HackerNews huggingface dataset:
My experience is that most Elixir devs are very excited about their language of choice, but also fair about the pros and cons. In fact, I've been surprised by this compared to the many other language ecosystems I've explored.

For example, while for many Elixir has been a 'step up' from Rails, most advice given, even deep in Elixir land, is that Rails might still be the preferable choice for a variety of reasons.

I imagine part of the reason is that most of 'us' don't use Elixir exclusively, so we can't just bail out of all other ecosystems and do the whole us vs them thing.

On the other hand, the above commenter seems to actively go out of their way to comment negatively about Elixir whenever it's mentioned on HN, and I still don't really understand why anyone would put in that kind of targeted effort.
I'm not saying it's economical, but anyone willing to pay 2.5x the cost of a Made-in-China phone could have their phone assembled in the United States: https://puri.sm/posts/librem-5-usa/

(No relation to the company, though I did once have a very nice chat with Todd Weaver).

And to the larger point: I agree completely that politicians opening their mouths about jobs (and also about anything else, IMO) is bad faith bullshit.
> (3) a replacement of the Electoral College with a popular vote

Replacing the electoral college with a popular vote is like deciding the World Series based on the total number of runs scored (instead of games won).

Sure it's an objective comparison of _something_, but it doesn't necessarily select the winner with the broadest and most consistent support.
Was that done to actively map your brain so that they could be especially careful around areas related to functions like speech?
> having to provide for the “welfare” of others.

It's only fair. Once you get old, the young and healthy will pay for your hospital stay, too, through the insurance mix.

But we could also just let you die because you can't pay the treatment.

You'll have to decide, there's no free cake in the end.
Pory turns 1 – Our journey to 100k in MRR (in transit)
Could you elaborate on the second statement? Why is that?
There is a great way to say "no": saying "yes, maybe later".
Same, I came to scripting languages (at the time that's what they were) in the 90s via Ruby. Now Python is my goto, for practical reasons, when I'm not doing C# or C++ but I still miss Ruby. I only have a vague idea what Rails is so I just miss Ruby itself.
> but I'd like to see these deals be more level-headed before they get to this point.

I don't think that's possible considering the incentives at play. Politicians always have the next election in mind, and what better way to try to win it then sign a deal that promises jobs? Doesn't matter if the numbers bandied about are too good to be true --- just get pen to paper and point the finger at your opponent and decry him as anti-business.
Would you consider this to be a very different thing from, say, a MiniDisc? Yet there is an Emoji for that.

MiniDisc makes sense for two reasons. First, because it's a legacy inclusion. Second, because absolutely, you might use it in a text message. "Don't forget to bring over your bitchin collection of [MiniDisc] on Thursday!"
It seems reasonable to argue the exact opposite: (edit: for clarification, I think this argument is roughly equal in strength to the parent. My bias is definitely showing, but my main point is that knowing which will be true is hard.)

Go was built explicitly to solve the real everyday problems of working in a large code base, largely driven directly by experience of several industry titans. It mostly remixes what has proven to work into a cohesive package. It's only as large as it absolutely needs to be (so new devs can learn it quickly), and has a strong focus on developer UX (gofmt, build speed, godoc).

Rust on the other hand is a far more ambitious language. It's trying to statically solve many types of problems which are typically solved through testing and experience. Using Rust productively requires much more Rust specific learning. With how Rust is changing and having multiple approaches to things as the language is defined, long living code bases are going to accrue different methodologies from whatever was popular when each component was written.

I think in 10 years a few experienced devs will do to Rust what Go did to C: Take the bits that obviously worked well, add a few ideas from other languages to soften some rough corners, and present it is a smaller, easy to use package. Though I also in general hope old languages are being replaced by new languages, as that must happen if as an industry we are getting better at building software. But also because I'm making a programming language and I have to believe I've found room for improvement for that to be a good idea.
Something similar happened to me recently: I updated all the pom.xml files to the correct version and then created the corresponding tag... in the wrong repository. Yes, wouldn't have happened with Git.
Looks like screen/camera sharing: yes, audio: no

https://lwn.net/Articles/849639/

Ed: or audio: yes?

> Pipewire support is now enabled which restore working screen recording and allow better audio handling for sandboxed applications

From release notes: https://discourse.ubuntu.com/t/hirsute-hippo-release-notes/1... posted by @spivak in another comment.
Just to keep in mind: StackOverflow deliberately removed Clojure from their surveys. People who embrace it are loving it to bits. Also Haskell and Clojure are not even in the Top 50 programming languages according to TIOBE.

"Languages not in the top 20 in 2016 are more likely to be used in new projects. "

Based on what statistic?

This is a wishful thinking article with very little basis in reality.
As much as I love ZFS, I also recently hit this issue and it was an exercise in frustration to get a running system again.
Goodreads Classics: Computational Study of Readers, Amazon, & Amateur Criticism
As the article talks about, the main driver of this mania is the historically low interest rate coupled with low returns from other investment sectors. So unless the cost of borrowing money in another country is in a similar situation, I would suspect not.

That said, Canada is in a similar situation despite the pandemic (or maybe because of it?) and the housing costs there are likewise crazy, if not more so than in the US.
The Flatpak version of Firefox is official and created by Mozilla. I don't think the Snap version is. If that matters to you then you may want to go with Flatpak over Snap.
the monorepo makes everything worse but it’s only part of the problem, i believe.

the big problem is forcing everyone to keep everything “updated”.

What is really needed is a way, given a certain state (branch, etc) to find a way to reliably reproduce the build artifacts AND to have a way for your software to depend on these packages at specific versions.

This way you can make an informed decision about when or if yo upgrade something and you know for a fact that (setting security issues aside) you will not have to touch the code and you can keep running it forever.

Look at virtually any modern programming language. The way the packages work makes of breaks the language. I never understood why Google seems to believe they are special and basic stuff does not apply to them, but it does.

Also, IMHO huge difference between how thing are run and work inside Google and how things work “in the wild”.
Go is the optimal language for a company that wants one (or more) microservice per engineer. It's a great language for padding out bulletpoints for a promo packet.
> Open source projects should rely on open source infrastructure.

Can you say why?
What's your interest in "fast" here?
I half agree. There is the notion that I actively don't like most of what is on the brown list. And I'm old enough to remember most of those things being new and have used a few of them. Also, I've done maintenance on a lot of code over the years (and still do). Including my own code. If you work products rather than projects and stick around long enough, this happens. Some stuff I've written in one language, I eventually rewrote in a different language. E.g. a lot of my early Kotlin code replaced Java code I wrote before. Kotlin made doing that particularly easy. These days, I rarely deal with Java code bases as I default to Kotlin for the last three years.

I've also done Ruby, Php and declined to ever touch VBA with a ten foot stick even when it was brand new. Just no. Php I never really liked but I appreciate what it does. Ruby was kind of alright but a bit limited for the things I do with it. I've deleted quite bit of it over the years. Some of it written by me.

There's a pattern that the author overlooks: the green languages address issues with the brown languages. E.g. Rust provides meaningful memory safety and other zero cost abstractions relative to C++. That's why a lot Github projects exist that essentially are about building better versions of classic unix tools in Rust. Also see the discussions about allowing Rust in the Linux kernel.

Kotlin was an obvious attempt to improve on both Java and Scala. Scala purists may disagree with that of course. The key issues there were lack of expressiveness in Java and the relative verbosity of that language. The issue in Scala that Kotlin tries to address is the complexity of that language. Jetbrains actually considered using Scala as an alternative to Java and in the end decided to create Kotlin instead.

With Ruby, people loved meta programming but the lack of typing made it less suitable for larger code bases. I've seen enough messy code bases to agree with that. There are several languages that you could name that ended up with a lot of former ruby-ists that basically feature powerful type systems, similar levels of expressiveness, etc.

So there's a progression of languages and programmers. Of course you use a green field language for a greenfield project. Why wouldn't you? Brown field projects are more common in this industry and rewriting them tends to be costly. So, that tends to not be a thing. Particularly successful things last a long time.
GP is noting the security limitations of Linux containers, the mechanism, not some management daemon like containerd or some API or workflow. firecracker-containerd is not a container, per-se, as stated in their README.

> Like traditional containers, Firecracker microVMs offer fast start-up and shut-down and minimal overhead. Unlike traditional containers, however, they can provide an additional layer of isolation via the KVM hypervisor.

I think the security mechanism of note there is the hypervisor -- a VM technology. The fact that it is manageable via a daemon/API that was created for containers, does not mean it provides security via Linux containers, the mechanism.

A similar story can be told regarding capabilities, a mechanism that is orthogonal to containers -- all combinations of with and without capabilities and containers have their uses.

I do think GP is overly glib and assumes a particular threat model in order to dismiss Linux containers so thoroughly, and you are right to note "they can absolutely aid in security posture", etc. But GP is correct to note that VMs (though also imperfect) provide certain kinds of security/isolation that Linux containers, the mechanism, cannot yet match.
We built the fastest voice chat app
And this is better than tmux... Why?
Perseverance rover just made oxygen on Mars
For me unit testing is very useful during development of new code as a way to ensure you cover all of your bases. But unit tests also give false security later down the road that old code still works fine due to the mocks and fixtures used to test with remain fixed in time.

Unless you actively update fixture data for all of your unit tests, you can never be sure that all green check marks means everything will work once in production.
I also had this happen. Literally almost the exact same, don't remember whether I opened my eyes or not but I remember hearing crunching sounds coming from my mouth and realizing it was them drilling or hammering or doing something destructive to my wisdom teeth. But zero pain. Just a wtf that is weird af feeling. But then I passed back out (not sure if they did something to make me fall back asleep or if it occurred of its own accord).
It's hard to say without more information. The context there looks Canadian so it's possible their providers were using Canada-only short codes. Sometimes providers change strategies on a retry also (I always have to click "retry" for Google 2FA but it always works on second try)
UPX creates anonymous pages that contain the decompressed payload, right? Those aren’t file-backed pages so how would the filesystem even know those pages exist?
GC and tracking ownership are orthogonal; the lifetimes of GC references and normal references would be different, but rust could perfectly well have a GC by default
Ah, thank you for pointers to the revived 2020 proposal (my radar to the L2 register was partially off at that time). I'm not sure that Klingon the script was in broader use at the time of the initial proposal though---there are several constructed scripts that enjoy uses comparable to Klingon's and I don't think they have been well received. Or alternatively, they all actually have a potential to be encoded but only Klingon speakers are enthusiastic enough to pursue.
> It is almost certain that in 10 years, both will be used more than they are now by several x's.

That's why so many threads end up being about Rust vs. Go. They are the new(ish) languages that appear most likely to be real factors in the industry for a very long time, so they bear more discussion.

I wasn't really around for it, but I'm sure there were lots of discussions about Java vs. C++ earlier in their lifespans, for this same reason.
“Non-Russian readers do not realize two things: that not all Russians love Dostoevsky as much as Americans do, and that most of those Russians who do, venerate him as a mystic and not as an artist. He was a prophet, a claptrap journalist and a slapdash comedian. I admit that some of his scenes, some of his tremendous farcical rows are extraordinarily amusing. But his sensitive murderers and soulful prostitutes are not to be endured for one moment—by this reader anyway.”

–Vladimir Nabokov. But of course he's being his usual contrarian self here; make of it what you will.
Emoji are for communicating to other people

This is an important point that most technical people miss. They want to turn Unicode into a cross-platform FontAwesome. That's not what it's for.

There are a lot of specific-use symbols in Unicode (chess pieces, for example), but those are legacy inclusions because many of those symbols were included in computers before the internet.
I agree that it is possible to write maintainable code in any language and it is possible to make a mess in any language too. But some languages to some extent trying to force this, which may move an average project, even if only a little, to more maintainable shape.

Examples of such languages are Go and Python: both to some extent enforce code formatting - Python with indentation being part of the syntax, Go with gofmt being almost universally used tool. Both try to maintain one preferred way to do things - opposite to "There's more than one way to do it" in Perl.
You can use abduco for that part (but I’ll just keep using tmux).
This is a great book. Thoroughly recommend getting it.
Create Longcats in AR
>Go was built explicitly to solve the real everyday problems of working in a large code base, largely driven directly by experience of several industry titans.

So have all languages, with wildly different philosophies about how to do that. We collectively just don't have any idea what we are doing. Clearly nobody has stumbled on a big win or one particular language would start dominating the industry due to the productivity bump.
Thank you for sharing. Intuitively I think your point makes a lot of sense. I don't think there's really enough data to really prove it, but I liked your approach.

I do think there's other stuff going on as well though. For example, newer languages are often designed to address perceived problems with existing popular languages. I'm a long-time Kotlin and Java developer, and Kotlin feels a lot like Java 2.0 - it specifically addresses a number of pain points people were experiencing with Java. So of course I'd rather be working with Kotlin, and going back to Java can feel like a drag.
I woke up while having my wisdom teeth taken out (doubt it was general anesthesia, but it was something more than local anesthesia). It was incredibly painful. Fortunately they noticed pretty quickly and did something and I was out again pretty quick.
This. I had very loving parents but i often wish they had shut up with the telling me I was special and smart and stuff. It was definitely a detriment to my life to be essentially taught that i could "IQ" my way through everything.
OP here. Can confirm. I was not envisioning an Arsène Lupin type character attempting to steal a jacket.
Good to hear that you like it. Munich can be lovely in the summer, you'll surely enjoy it. Also: Enjoying a real bavarian Biergärten is something I really look for after Corona.
I highly value articles like this one -- open and honest; it peels back the beautiful veneer to show great work has obstacles and perfection is always a struggle.
Isn’t it also true that newer languages might have learned from what made older languages hated? Isn’t a massive confound the possibility that language design as a field is meaningful and people are actually improving languages still?

I know the article mentions this, almost in passing, but it seems hard for me still to separate the size of the bias towards greenfield and against older languages and I don’t feel they adequately addressed it. The fact that python is definitely a “brownfield” language for me but still one I reach for and cherish as well designed seems to suggest that language design matters more to me.
Ever since I first started working as a developer, I've wanted to preach the idea that code UX is important.

Some issues I found:
1) It took me years to clearly specify what clean code is.
2) I still haven't learned to effectively articulate its importance.
3) Except maybe onboarding time, I don't know how to measure its importance.
4) Cleaning up code is not rewarded.
5) Writing dirty code is often rewarded with promotions.
I pay for my own healthcare insurance, as healthcare is not free in Germany. So your points are invalid as far as I’m concerned.
That doesn't conflict with the statement. If the IRB looks at something and exempts it, it has no reason to report that to the hierarchy in any way, because that's a routine process.
I think there are ethical questions for the beneficiaries. Isn't like subjecting someone else to intense pain for an hour in order to receive money?
Here is it:
https://releases.ubuntu.com/21.04/
Why 19.10? (I mean, why not 20.04 lts?)
And in what aspect is Go a better than the million other language with GC? Like, it is C level bad at expressivity, way too verbose because hardly any abstraction can be made there. Concurrency is the only thing going for it.

But how is it any better than Java or C#?

And Rust is a low level language, so it has to get away with rare cases where a GC is not applicable. And being low level of course imposes the memory layout of the program on APIs as well, but that is a known trade off when one goes low level.
as an English speaker I should note there is some ambiguity about the phrase 'going back to', it can be used inclusively or exclusively but most commonly is used inclusively so what you said strongly implies that you also think Pushkin is highly overrated?

But even if you were using exclusively it would mean you thought that everyone after Pushkin was highly overrated. Are the people who were averagely rated to be rated poorly then? It seems unlikely to me that so much of a vast nation's literature, for so long, can be so overrated.

vastness implies lots of writers and resources.
This is absolutely fascinating. You could use this picture to play the worlds hardest game of I Spy:

I spy a construction worker with his hat on backwards
Well the money still needs to be paid at some point. If you go the 10% deposit route, you will get slightly worse interest rates and overall higher monthly payments. Payments that you need to maintain for ~20 years…
Is there a correlation between having a degree and competence? Because my experience is that there very much isn't.

I would go so far as to say that the information age has made educational material so widely and easily available that the only value universities provide is signaling and wealth/class filtering.
A few thoughts:

1. This is amazing. I wish I had it years ago, and I could use it now.

2. I like the visualization but my favorite thing is the sense of completeness and influence I get when I look at articles. Rather than relying on someone's opinion of the most influential article, I can see the article and the influence right there.

3. This is early days but I am already running into the frustration of not being able to see all the articles out there. This probably has to do with publishers and paywalls and what not, so probably not your fault, but it is still a problem that has to be dealt with in order to render this truly useful. ()

() interestingly, over time, it may not matter as much when every paper has a version on ARXIV, but in 2021 I was looking for papers influenced by work done as far ago as the 80s and 90s.
Or the binary tar-ball from Mozilla included the auto-update.
(I'm using Nightly so that's the best option for that)
Why does it sound implausible? In any uni I've interacted with, profs did pretty much their own thing and without a reason very little attention is paid to how they do it (or even what they do).
In a simulator, I can live with my parents forever. In real life, I might get about a day or two.

Most people want to date and find a spouse. Most people want friend groups they have a connection to. Most people want hobbies that are interesting and fulfilling.

Being healthy is not free. Socializing, reasonable physical fitness, food variety.

Sure you could live in the mountains socializing with squirrels and doing pushups all day which would save you a lot of money - but it would not be the life most people want.
I have a similar situation at work. What about making this script more generic, factoring it out into its own repo and referencing it with Git submodules or SVN externals? You could also think about turning it into a proper plugin for the package manager.
The actual crime would be different; the former would be assault, while the latter would be unauthorized access under the CFAA, but I think the principle applies to both. In both cases the intent to cause harm exists, and doesn't become irrelevant just because the victim had to put themselves in a situation to trigger that harm. If anything I think there is a stronger case against leaving exploits around where software might scan them, because while stealing is illegal, scanning files typically is not (if you have legal rights to access the device, via ownership or warrant).
Create Azure AD apps from the manifest