skysight-inc/HackerNews huggingface dataset:
I don't know Ada well personally, but from what I've read, it's a bit less advanced than Rust at static checks, a good bit simpler than Rust and Swift but more complex than Go, and a little bit old-fashioned in approach (verbose syntax and all that). But I'm not very educated.

I would say that Ada and Rust probably compete on some things, but given the history of Ada in industry, it's probably only in fields that already use Ada (aerospace and what-not).
It is not sustainable when we have an unsustainable and quite frankly insane monetary policy which is being pushed by central bankers. In a sane world credit provision would be decentralised and provided by local banks who are close to the borrower rather than people sitting 1,000 kilometres away. Remember: the most important role of banking is not the provision of payment services (although that is important too), it is to intermediate between savers and borrowers (which is almost always done better in a decentralised system).

Indeed the current centralised banking model is quite recent and only started to creep in after the enactment of the Federal Reserve (and the consequent central planning of money and credit) and dramatically accelerated after the end of the gold standard in 1971 and the decoupling of money from sane fundamentals. It's not a coincidence that what followed was extreme consolidation of banks and the quasi-neofeudalism that we see today with large corporates who are able to get credit from large multinational banks which they are close to and then with that money price out small businesses and drive them to bankruptcy.

What has been happening for the past 40 years is not natural, and what banks are doing now is almost entirely driven by central banks and not some natural order resulting from the free market (which throughout history has always selected a decentralised banking system with thousands of small local banks). In my opinion we need to protect what little we have left instead of just yielding to the central planners at the Fed, the ECB etc.
I guess if you're talking about a subset of the 31% of graduates who don't have student debt, you might be right. [0]
Sure, it's not top 1%, but it's certainly closer to the top 10% who have this luxury, as opposed to, say, the median college graduate.

---

[0]: https://www.cnbc.com/2019/05/20/how-much-the-average-student...
"It looks like you're running low on {product}. I have ordered Amazon Basics {product}. Please check your email if you would like to cancel the order in the next thirty minutes."
Show HN: The minimalist CSS framework, Neat
and they get prison time.
Video https://www.youtube.com/watch?v=zEoQrGY7OJM
> But by the same token, Vim is arcane compared to Notepad style editors but is quite popular, so I outright reject the hypothesis that Emacs has lower numbers because it's arcane

vim might be arcane compared to Notepad, but I've been successfully using vim as an editor of choice in ssh pretty much throughout the whole uni without knowing more than :w and :q (at which point it basically was a notepad). I was ever completely lost in Emacs though, with its nested C-x, M-x seemingly without rhyme or reason. I wouldn't "outright" reject that hypothesis without more scrutiny.

Anecdotally, I've been an Emacs (Spacemacs) user for a few years after that, and I never got used to all the commands I would use on a daily - but not hourly - basis, having to always look those up. But, as one of the other top-level posts said, what made me switch in the end were the language servers.
Misfires on a spark plugs are pretty obvious though. Maybe changing the air filter or cleaning the intake manifold is a more apt comparison?
Yeah the Soviets hit mars in the early 70s; we barely had memory chips at the time.
Well, what actually happens is that there's less pressure on web developers to make their sites faster (in contrast to other business goals) and so we reach a new equilibrium where sites perform just as badly.

Web developers aren't alone here, of course. It's the same story for systems software as well.

In general, thinking in terms of equilibriums is helpful.
Not all coders are good coders. If your manager was the opposite of what you strive to be, your work probably won't make a good impression in their eyes.
The Techade Quiz
He is not you, I am you.
I don't think it's monstrous to eat an intelligant animal. Pigs are very intelligent and sensitive animals. And yet, I eat pigs without remorse because being born on a planet where animals eat each other is not something I chose, therefore I do not feel guilty about it.

Also, it's still mosquito season in Greece where I'm currently located and I've been feasted upon often enough myself to know that refusing to feed on another animal is a peculiarly human exceptionalism. In fact, I believe its sole purpose is to place humans apart from (indeed, above, morally speaking) every other form of life on this planet.
Also, through the various *Kit libraries and now (sooner or later) SwiftUI, Apple is staking out a rapid-development territory that will be hard for the other ecosystem(s?) to match.

So, if you have to choose between making your app for iOS first, or Android first, then in addition to any consideration of markets which might or might not apply to your business model, you will have a very strong incentive to choose Apple for time to production.

I would love to see more serious competition on that front.
Haiku's logo was a contest or a vote at one point, as was the name Haiku.

Sort of a tradition :)
This is very insightful, thanks!
HTTPS is worse than security theater
> maybe pijul is different

No "maybe"; that's the point. Why does modelling something fundamental, like conflicts, decrease confidence in the approach?
I don't think we're talking about the same thing, because according to what is classically meant by spiritual enlightenment, you don't "achieve benefits through enlightenment". You certainly don't "achieve" anything, and there are no "benefits" to spread.

Perhaps that may sound somewhat paradoxical, but that kind of paradoxical understanding is somewhat representative of enlightenment as a whole.

Can you really think of anyone you believe to be truly enlightened spiritually, who is busy trying to "spread it to as many people as possible"? I think the answer is no. The enlightened may help you out if you seek their assistance, but they are almost the exact opposite of "evangelicals" who seek to spread a message.
It would be irresponsible not to, even if they aren’t deployed. At the very least I don’t think you stand a chance of anticipating or defending against attacks if you aren’t developing them yourself.
I've been gradually switching towards completely using IDEs for like 8 years now, and in the past 2 or 3 I've broken free completely. Some of my symptoms are the same as yours: Frustrating package management, obvious missing gaps in functionality.

My conclusion is slightly different: I don't need a text editor anymore. I need an IDE and it's a bonus if it's a good text editor.

Efficient text editing is nice. But I spend a lot of time jumping between files, looking up definitions, reading documentation, tracing through code, debugging, comparing tests and regular code, etc. Plus all of the features that you expect: (colorblind-friendly) syntax highlighting, syntax highlighting, linting, etc. This is where the package pain comes in. I don't want to figure out how to configure the cross product of "every single IDE feature that I need" and "every single language that I use." I gave up. It's too much. I want my environment to either do it by default, or install a single plugin per language and never think about it again.

I'm not sure how Emacs can get "more modern," because being modern would likely start from the premise that you'd need to allow the core innovation of IDEs. They provide a pluggable framework to get uniform behavior across every language that you use. That ship sailed in Emacs - how do you move away from 40 years of "we ship a vanilla experience and you customize your environment completely to your own liking"?
I have participated in a few hackathons. My teams have won some. And they have lost some. All of the ones I have participated in were 24-36 hours long. This comment is probably not that useful for OP, but I will still publish it anyway. Here is my (current) recollection of thoughts:

- In these short hackathons the probability of winning is inversely proportional to the amount of new technology you are using. I have seen teams quit because they got stuck in a particular issue and couldn’t finish their prototype in time. A similar thing almost happened to one of my teams. This is also a bit sad because it means that improving your chances to win implies reducing your chances to learn.

- Leverage frameworks, libraries, and templates. My go-to example for this one is a web server. Imagine your team tries to implement a web server in C. If the team you’re competing against uses Django you are going to have a hard time to compete.
My secret leverage is Unity. With Unity, you can create something in 3D very fast that looks nice with very few assets. Remember, unless the jury explicitly says otherwise, they care more about the product than the code.

- Get your team on the same page. Because of the previous points, the worst thing that can happen is that some people on your team try very hard to win while others are just in for the experience. This will create friction. Get your team on the same page before starting. I can’t emphasize this one enough.

- Clear communication. On one hackathon one of our members left for dinner for what was going to be 2h. He was absent for about 4-5h. What annoyed me from that experience was the lack of communication in our team.

- I like to think before the hackathon starts there are no leaders, only developers. I believe leaders on short hackathons raise to the occasion on the spot. I’ve done it. But that wasn’t predetermined by any agreement. I’ve also followed people who led me. Whatever your role is, remember: you’re not an authority; don’t act like one. Responsibility is always collective.

- Principle of least effort. I’ll repeat it: Your jury cares more about the product than your technology. If you only have 24 hours, then you don’t have 2h to spare to discuss the design. You should optimize the ratio of results/time.

- (Post-Corona tip, whenever that comes) Come prepared. Come with Ethernet cables. A switch or two. Your batteries charged. I’ve seen wireless networks go down on these hackathons. On that occasion, our team didn’t even notice it because we were wired in.
Not defending FB here - it looks like they have acknowledged their faults in this issue specifically.

That said, this argument structure sounds a lot like "US leadership was warned about the attacks on Pearl Harbor". It looks like FB under reacted to these warnings, probably because they didn't realize how bad the outcome would be. How can info/escalations be presented so as to break out of the noise? (I'm assuming here that FB also has been warned of a lot of really bad things that never came to pass, which isn't something we can know - but it's an interesting thought experiment.)

What is the expectation in terms of separate the signal from the noise? How can the critical factors be identified ahead of time? Was it foreseeable that the targeted hate speech would turn into violence? What level of reaction is appropriate, given the uncertainty of hate speech -> violence?

Apologies for the brain dump - not expecting answers to all of them. And not defending FB here. I just think these types of questions are very interesting (plus I just read Superforecasters, which examines similar decision making w/r/t the decision to kill bin Laden).
These are adults, not children. Quarantine measures applied to adults based on age are unprecedented and unjustified.
> the dog can't alert you when you're not home

That's a business model right there!
That doesn't give them a right to own 100% of the activities built atop their devices. Not when these platforms capture every conceivable human action or transaction. They should have lost that privilege when their reach grew so broad and deep. (It is a privilege that the US allows them to conduct business, and that can be altered.)

If Apple put up a bubble around 40% of all Americans and you wanted to give these folks air to breathe, would you be content to pay Apple 30% or be forced to go through Apple's slow moderation and release control mechanisms? Keep in mind that they may shut off your ability to provide oxygen at any point in the future for any reason.

The correct model was Microsoft Windows. You pay to license it, but then you can execute anything you want on top of it. If you want to pay Microsoft to help with distribution, you're free to do so. Microsoft is still making bank.

What Apple has done is uniquely controlling and prohibitive. They've captured all computing-related economic activities for a large percentage of the population. You shouldn't be allowed to conduct business like that in the United States.
My dad (in his 50s but in great health/shape) got a flu around the same time that you did, and had similar problems. Felt flu-y for 3-4 weeks, and then for months afterward he felt weak, had an elevated heartrate, and would get winded walking up his driveway. After a few months the VA finally saw him and they put him on a beta-blocker, which helped. It really reminded me that a random fluke illness can put you down for months. We tend to think of illness as a binary; it's either something quick that you get over in a few days, or something chronic that you will have for the rest of your life. Maybe we should be thinking of viral infections more like we do orthopedic (or psychological) injuries: something that you can adapt to and mostly recover from pretty acutely, but you might need to take it easy on that bum shoulder and it might flare up occasionally.
If you went through the process yourself by hand each pencil is hilariously time consuming. But with giant machines mining the graphite, logging machines cutting down trees, trucks transporting both, going to a mill and then a factory to combine them, the amount of labor per pencil is minuscule because it gets spread out across millions of them. In medieval times you don't get the benefits of automation and mechanization, it's grunt work all the way down.
It looks like a good story about a weird corner of that industry. That seems on topic to me.

I posted a related explanation in an unrelated thread if interested - https://news.ycombinator.com/item?id=24594315.
My advice from leading shorter-term hack sessions at work and game jams:

1) Emphasise that the primary goal is for "us to have fun". This immediately takes the pressure off, and helps put the 'thon in perspective.

2) Emphasise a secondary goal of "getting something complete", regardless of whether it's the perfect product or not. For gamejams, it's usually a struggle to get a fully-buildable and playable game out the gate, so setting expectations low re: functionality makes sure you at least have a working product at the end of it. Once you have that, you can focus on incrementally introducing features. Again, this takes the pressure off.

3) Think of it less as leadership, and more of a case of "filling in the blanks". In those times where there is a bit of silence amongst the group in terms of what to do, simply speak up and say what you think could work well. Others will often be happy to just accept that and move forward.

4) If someone else has strong feelings about a certain decision or direction, hear them out and go with it if it makes sense to you. It's more about exchanging ideas as equals rather than the "leader's" way or the highway.

5) Your leadership will come most to the fore when it comes to coordinating a completed product as time wanes on. Often the team can get caught up in what they're doing, so you need to push a little to make sure things are on track. Things like: "OK we have 2 days left. Shall we draw a line in the sand with the database by 12 noon, and then just focusing on tidying things up and making sure there are minimal bugs"?

6) Proactively offer to help or contribute to what other members of your team are doing throughout the 'thon. A good way to to this is to have something specific in mind to contribute, and ask the person if they are OK if you do that. This takes the pressure off them to come up with something you can assist with themselves. Doing this role models good teamwork to the rest of the team, and they may start doing this amongst themselves too.
If it's on a gate it could use two electric wires that touch when closed and open the circuit when the gate is open. Of course that would have to be hooked up to a sensor.

I'm not sure what the laws are there, but I'm guessing this is next option is illegal there as it is here. You could hook the metal gates to an electric line. The screams would alert you.

The other way to do it is to use tripwire line or braided fishing line hooked up to an electronic alarm (pulls a pin or tab to alarm) or ammo blank alarm (pulls a trigger to fire the blank). Put it a few inches off the ground or attach it to a gate.

You can also use lasers as a tripwire device. They make them for driveways so it will make a doorbell-type noise to alert you that people are coming. This could be a great option if you have to come down a driveway or path to get to the horses, but you may get false alerts with deer. You can also use this between your outer and inner fence (if you have that style).
I'm crying.
Redis changed from AGPL to Apache 2 with something they called a Commons Clause, then finally to Redis Source Available License because of cloud providers. Don't really know exactly which event triggered the change, though. I suppose it could have been GCP or Azure instead of AWS. Regardless, AGPL is far less restrictive than people claim it is. It is a particularly strict version of the GPL, but given proper legal review it is unproblematic to use commercially, which cuts both ways as Redis found out.

I think there's a serious amount of FUD around it. I suppose it's because of how rare it is. With more usage, it would probably bee seen as less dangerous.
Yep: I worked in finance for years, have degrees in economics...and their coverage is useful.

To name one example of many, they were saying that JP Morgan was rigging commodities markets for years. I know people not in finance who heard that ZH story (years ago now, when ZH was in their pomp): lololol, tinfoil hat...that JPM were rigging commodities markets was known in finance for literally decades, it was common knowledge (I didn't work in commodities and heard about it, JPM were just fined $1bn for it).

I think people get confused because they have trouble signal from noise, particularly from people who are obviously biased (this is a key ability in finance, almost all the information you receive is conflicted, and you have to understand human nature at a deep level i.e. understand what people lie to each other about, what they lie to themselves about, etc.). I am totally fine with biased coverage (everyone is prone to biases, it is just some people deny that to themselves/others). I don't have to believe everything they say and, compared to every other finance publication, they really do cover stuff that no-one else is covering. Yes, it is sensational and their political coverage is usually insane (tbh, it is quite funny)...but, again, that doesn't mean they are wrong about everything or add no value (btw, almost every economist I have ever met has had bizarre political views...people who work in finance usually do because being an expert in one thing does not make you an expert in all things).

In my experience, people who talk about news not being reliable also believe all kinds of insane shit that appears in the mainstream media. Believing that you are hyper rational is, in itself, not rational.
In my personal experience, Swift occupies the sweet spot in between Rust and something like Python for application-level programming. It's a modern and well-designed language with a Rust-like strong and expressive type system, including useful generics, powerful enums, and safe error handling. It also has fairly straightforward memory management, really straightforward polymorphism, seamless C interop, and good performance -- though it's not quite as fast as Rust because it prioritizes ease of use over zero-cost abstractions.

So no, it doesn't really have a whole lot of "innovation or originality" -- but it essentially takes some of the best ideas of modern language design and wraps them into one general-purpose language for application development, and as a result I find it to be a really useful and practical language.
They switched to Yahoo for a while.
I thought I knew Fubar’s etymology, this article deepened my understanding a bit.

I don’t know why I enjoy this kind of word history, especially the speculation on what language a word derived from. Thanks for posting this, it was a fun read for me.
I was just going to say this. You can get the blueprints for any home in any city just by requesting it from the local city hall records department.

You typically have to pay for it, but it is not particularly expensive. It's part of the process if you plan on buying a property, in order to ensure everything is up to code, property lines are where you expect them to be, etc.

Unexpected easements can be a real bitch if you buy a property only to find out part of it isn't actually yours, or that it is technically infeasible to update or rebuild a portion because of an undocumented/illegal code variance.
It's a physical product, so currently Apple isn't attempting to levy a 30% charge on the transaction.

Apple is having enough trouble getting retailers to accept Apple Pay as it is; attempting to tax physical sales would kill Apple Pay and likely bring about the immediate ire of pretty much every government of every jurisdiction they do business in.
Recording equipment, on the other hand...

Time to rent studio space!
I think I still have the .emacs file I inherited from an upperclassman. It had better syntax highlighting than what was built in at the time =)
Neat! I've been working on something quite similar: https://github.com/hoytech/quadrable
Vim drops noobs straight into normal mode, meaning the moment they start trying to type they get confused. I know that's what happened to me. The arcane nature of Emacs doesn't make itself apparent nearly so fast.
Edit natural language documents without wasting about 1/4 of your screen width on useless column alignment information.