skysight-inc/HackerNews huggingface dataset:
I'm not incredibly knowledgeable about AWS and Docker, but I have a couple questions for you:

- How would EC2s compare to Fargate ? I encountered situations where, running the numbers, I much preferred having my own set-up with images ready to deploy + adapting my EC2 instances to the task, instead of dealing with Fargate's convoluted restrictions and definitions

- Has your colleague tried to increase the disk size given to Docker? I have seen on a few macbooks that this made a world of difference for CPU usage, and I thought I'd pass on the information if it hasn't already be tried yet
or people could just start infecting each other
The zoom guys are ex-WebEx guys. I saw the same zoom-bombing problem in WebEx few years back. we just enforce adding passcode/PIN to each meeting to remediate customer escalation.
It wouldn't be the worst idea, which is why I'm not optimistic that it will play out that way. At best, given that states administer unemployment insurance, I would expect to see a patchwork, with many of the states where it's most needed refusing to implement it.
Yes you can, but if you do that you have to release the Object files and make it possible for the customers to link them to their own Qt version.

This is a much greater hassle than just linking dynamically, so we don't do it.
> Even in the U.S. I’m not sure where this myth of SWE being the most well paid industry comes from.

Because it basically is.

> Try many finance jobs and big law, also medicine in certain specializations.

Selected finance jobs aren't an industry, neither is “medicine in certain specializations”, neither is big law (law as a whole is an industry).

> It’s also well known that to be an incredibly high paid SWE, you need to be at a large public tech company

To be incredibly highly paid within SWE, sure. SWE is still highly paid compared to the rest of the world outside of those firms, and an unusually accessible high-paying field, without any post-baccalaureate education requirement, or even a firm requirement for an in-field bachelor's degree.

Note that there are similar (and often much bigger) cliffs in other highly-paid industries (which your allusion to “big law” implicitly recognizes.)
Things got better, of course. We were doing pretty well until 2008, when we weren’t doing so well. Then we did pretty well again. That’s the nature of life, isn’t it? It oscillates, like a sine wave, like the rise and fall of your chest as you breathe in and out.

Call it intentional vagueness if you want, but I think the author's point is: this too shall pass. The particulars of the author's story are likely so specific as to be useless.

There are ups, there are downs. Keep calm, and carry on.
Seems very relevant to many existing SaaS services today:
1. They are not doing CD, but they do deploy frequently.
2. They are using K8s, or even immutable infrastructure, so far as I can tell.
3. They have a lot of people involved in maintaining their deployments system.
4. Speaking as a user, I do not recall many significant outages, so on the surface, it seems that they have sufficient reliability.

Speaking as a heavy user of Kubernetes, evolving from an existing VM-based application to something like what Slack is doing seems like it might be more sensible than a "move everything to microservices and Kubernetes" modernization strategy.
It's also about how many galaxies (and other critters) exist in the universe, that you can scan enough to find two colliding galaxies at just the right time to view the jet.
Shock Wave was my favorite as a teenager! Inca Gold was a close second.
What breaking changes have gone in since 2000 that didn’t break a change added after 2000?

Auto is the only one I can think of.
Twitter will now share more user information with advertisers
The biggest problem of Qt is the FUD just like you're spreading.

No. All is LGPL except for some niche libraries.
I had a similar problem when I started using Redux for a side project. If it's a simple enough app (as mine was) try https://www.npmjs.com/package/unstated. I am not a React expert but this was super simple and easy to get up and running with.

[No affiliation with the project]
How I made $2.5K MRR from MarketingExamples – Story of MarketingExamples
Coronavirus Disruption Puts Supply Chain Software to the Test
That does seem a bit weird - especially as Mesopotamia is also included in that list rather than the modern countries in that area.
So how can reality be determined when employment has become such a facade?
Listening to Study Music During Sleep May Improve Test Scores
Brown's accelerated CS course https://learnaifromscratch.github.io/software.html teaches graph theory, big O, some compilers and all the assignments are things you do in industry like writing a program to test another program.
They’re kinda fucked because differential analysis was coined long ago to describe a set of techniques for attacking bad cryptography.

Differential programming would be less flashy but may be confusing.

I wouldn’t actually be interested in this topic much except for the top level comment complaining about them wanting a new version control system for this and now I’m a bit curious what they’re on about this time, so will probably get sucked in.
Sure. This is moving the goalposts though: you initially said "when will this be finished?" It is clear that C is not finished.
Overrated. In what kind of application do you need this? In the vast majority of React apps you do not need this.
> The rest of the family were saved by what they regarded as a miracle: a single grain of rye sprouted in their pea patch. The Lykovs put up a fence around the shoot and guarded it zealously night and day to keep off mice and squirrels. At harvest time, the solitary spike yielded 18 grains, and from this they painstakingly rebuilt their rye crop

Think of how long they watched this little shoot of rye grow... that must have been a really scary period.
Redux Toolkit https://github.com/reduxjs/redux-toolkit solved the problem of having too much boilerplate for me. Slices also make it organizing state a breeze.
And this is why Ext.Net is so expensive. Sencha is the one who decided to hike the price.
HIPAA, GDPR, CCPA, Right to be Forgotten, DMCA

The ideology is law, most blockchains as is do not comply with law. So the are effectively unusable in practice (generally speaking too)
> how tiny and insignificant we all are, although we think different.

I figure the significance of humans is that we are sophisticated enough to recognize that we exist, not that we are physically large or emit many photons.
We all don’t get to waltz into a new job and say ‘Hey remove all this verbose Redux code and app structure, it’s slowing down velocity. Plus this crud app is too simple to add this annoying layer of boilerplate’.
> and though he steadfastly refused to believe that man had set foot on the moon

Prescient for somebody who doesn't even know what a soundstage is.
> Its Secondary Market facility may purchase U.S.-listed ETFs. While the preponderance of those holdings will be those primarily focused on U.S. investment-grade corporate bonds, the remainder will be in ETFs whose primary investment objective is exposure to U.S. high-yield corporate bonds.

In other words, the Fed is buying junk bonds through ETF. There's one more stage to go: buying equity ETFs, like the Bank of Japan has been doing for years.
If people weren't dying, it would be hilarious had badly understood this epidemic is. Months since the start, we have no idea how infectious the virus is, how many people have been infected, how deadly it is, how effective (or not) containment is, how many people will need to be hospitalised or how long for.

It's actually incredible. I'm very cynical, but I wouldn't have believed Western governments could have floundered so badly if I'd been told even a month ago...
Yes. I've used Rust (in a hobby capacity) for a couple years now, I've written a fair amount of C++ and have a clear understanding of how pointers and references work, yet these two cases you mention sometimes remain mysterious to me. I've developed an intuition for "how to use them" but I don't always know exactly what they're going to do, because their meaning shifts under my fingers to try and match up with what's most convenient. I've just learned how to fiddle with them until the compiler accepts them. There's a fog over the code when they come into play.
In my opinion, there are two main factors driving this:

- Lower spec devices have a hard cap on overall code complexity imposed both by available ROM or flash constraints (big projects literally won't fit on the chip), and by time constraints (if your chip is running at <= XX MHz when it's active, you don't have time to run very many functions between events or interrupts). Most projects for these devices won't grow to the point where you really need the code organization benefits that C++ provides.

- It's a lot less effort to port or implement a C toolchain for your chip than it is to port or implement a toolchain for a more complex language like C++, Rust, or even Ada. It's not just the compiler - you also have to have a working standard library (even if some functions are just stubs), an interactive debugger, and integrations with IDEs (if you already provide that for C). All that software engineering is expensive, and you have a much smaller market of developers to amortize that cost over.

These constraints aren't as binding for high-production, higher-spec devices like popular families of ARM Cortex-M chips, so usage of C++ seems to be relatively more popular for those devices. Even then, embedded work normally requires more of a "C with classes" or "C plus the std::algorithm library" approach, which is different from C++ projects you'd see that target servers.
It shocks me how few people understand market equilibrium and supply/demand. If demand increases, price goes up. Would you prefer to be able to buy what you want at an increased price or not at all because there is a shortage? I would prefer the higher price because then I can actually get the item.
That seems pretty ridiculous coming from Linux, where the vast majority of software will be installed via a package manager, making clean removal trivial.

Under windows, I would consider any software that requires a separate removal tool to be suspect. Software wanting you to download a separate tool, fill out unavoidable surveys or linking you to a site to track uninstallations is all very seedy practices.

Why isn't it expected of Mac software to keep an installation manifest and provide a way for removing the software?
Small Town Texas Girl Making Big City Moves
> I guess the syntax was already a given, so they just did it regardless of the criticism

This is not true. Several people on the lang team (and many community folks) changed their positions several times over the course of the debate.
Spot on! The fruit has a natural protein which temporarily and harmlessly binds to your sweet receptors. Unlike other sweeteners which directly activate the receptor, this one indirectly activates the receptor only in the presence of acids.

This mechanism gives it loads of unique properties. One, the protein has no taste and doesn't have the same chemical/bitter aftertaste of the other sweeteners out there on the market. Furthermore, it serves as a food flavor enhancer just like any other herb or spice. You're not just sweetening the food, you're removing the unpleasant tartness and bitterness of foods that otherwise mask the taste of the food. Discover the hidden natural flavors of your food. Finally, since you're affecting your tongue instead of the food a single serving will last you 30-60 minutes, the entire length of a meal. You wouldn't need to add more like you would otherwise with other sweeteners if you were having a breakfast of coffee, yogurt parfait, and grapefruit.

Don't worry, it is not only natural but also completely safe. Coca Cola published a study on the protein in 2019 saying it has no potential long-term side effects. There is also another study published in 1974 where they gave rats 10,000 times the regular dose a human would take...every day...and found no side effects across several generations.
That's exactly right! The argument is that if you look at truly reliable cloud services (think Google). They already use consensus protocols to replicate the database globally for fault tolerance purposes. The spanner paper does a decent job explaining their architecture.
https://static.googleusercontent.com/media/research.google.c...

Why not do it for decentralization purposes too?
Blockchains are just a another class of consensus protocols. IMO one of the defining aspects of blockchains is the stronger threat model. Traditional consensus protocols are designed to be crash-fault tolerant, not byzantine-fault tolerant.

I wouldn't get tripped up by the word "validator". In the academic world we probably would have used the term "node" or "replica". It has a special meaning in the blockchain world because it conveys a sense of trust and work-checking.

"Who pays" is a fantastic question. The blog completely elides the question about incentives which in my opinion will vary depending on the app. For creating an censorship-resistant Wikipedia, it'll be different than a communications app. Hoping to write a blog post about that soon after we get more built to show.
I don't agree with everything here. Open source really does mean that you just have all the code to rebuild the thing from scratch under the right sort of license. Open source doesn't mean anything else, like having access to design decisions.

Interaction style and personalities are also not part of the definition of open source; open source doesn't mean nobody is brusque or abrasive. Some communities have additional codes of conduct and social contracts and what not for that sort of thing.

Here is a balanced viewpoint from the GNU Awk and Bash maintainers:

http://www.skeeve.com/fork-my-code.html

Elm users who are not happy should fork the code --- everything, including the ecosystem's dependencies on an ELM internet domain --- and maybe produce something that is completely self-contained. Software that relies on "phoning home" is a risk regardless of where that is hosted and whether the people are nasty or nice.

If the Elm core developers don't like it and kick people out of their project for forking, you just have to bite the bullet on that.

(From the description of what that project is like, why would you care about being kicked out. Kicked out or not, your 20 line bugfix still isn't getting looked at for another two years.)
Marketing giant Maropost exposes 95M email records and doesn't care
A tool for hiding your online assets from online scanners
Is it naïve to blame the whole system that has created a need for these weapons to exist in the first place?

By "whole system," I mean the environment that makes these things "necessary."

Or, is this also pushing responsibility onto something else?
Do people keep their Bluetooth on? I don't for security reasons
In general, programming languages will change over time, so what matters to me is how that change is managed. Cautious, small, gradual changes over time seem safer than big releases every year or so, but particulary because of Rust's approach to stability. When Rust has a new feature implemented, it does not immediately become part of the stable language. Instead, Rust only commits to stability for a feature once it has been properly tested. It's something I think PHP (which I have been a significant contributor to) and other languages could learn from, because there's no substitute for real-world experience to decide if there are remaining rough edges on feature, or whether it is good idea at all.

Moreover, unlike some other languages, Rust has chosen not to force people to adapt their code to new syntax and features! They can stay on an old version (edition) of the language forever, yet still use an up-to-date toolchain and have others be able to make use of their code. I wish every language was like that. Imagine if Python 2/3 had never happened.
> The result of 500 hours of work in After Effects, Photoshop, Illustrator and Premiere goes by in 3 minutes, 44 seconds.

1000:1 ratio of input to output.
I’m not even sure if this would parse as legitimate English. What?

And in response to your other recent comment, my entire family has been “consumed” (you idiot) by one disease or another. I am the only one left. Nobody was hysteric when they died. People were apathetic. It’s difficult to sympathize with people’s hysteria when just a month ago they were apathetic in the face of countless lives lost to other preventable diseases even though there were easy prevention methods available. Difficult to sympathize with the hysteric mob when a month ago I watched them stream from the back doors of bars, staggering into their vehicles and driving off - the same drive of stupidity that fuels the hysteria and apparently your comments.
In the US maybe, gig economy is global though.
I think that complaint usually comes from people who try to put everything related to state in Redux, and not just the parts of it that need to be.

Also the 'reducks' pattern of splitting the Redux state into separate files, each containing a reducer and the related actions and selectors helps keep things simple to understand (although I guess it is a bit more overhead, actually).
I think this is a case where "Think of the children" is the right answer.

Someone uploads pictures of a child being violently sexually abused to a blockchain. It is my honest opinion the majority of people would not want to continue distributing those photos. It is certainly the law of many countries that it is illegal to distribute such pictures.
You may find WordGrinder by David Given a treat. It is the most close resemblance of WordStar experience nowadays and it is free.
https://cerebraljs.com/
This post resonates with me. I'm not deeply involved in Elm, I just have an Elm side project (started on 0.17) with roughly 1k lines of code.

Do I love Elm? Yes, definitely. It's such a well-designed language. Lots of thought went into it. It's very focused and has great (albeit sometimes non-obvious) solutions for almost everything.

However, the leadership style is also what keeps me from recommending Elm to anyone wanting to create a project that cannot be simply rewritten in case Elm does a change that doesn't work for you. I wouldn't use Elm at work, since it would be a very high-risk situation. (In fact, I was faced with that decision and decided against Elm.) If you face a blocker, you're screwed.

A version of Elm that is being developed in the open, where people are allowed to make suggestions, where all feedback is considered valuable, where people can experiment and explore the design space without artificial limits? Yep, I would love such a thing, and I'd happily contribute.

Until that happens, I'll happily use Elm for small, personal low-risk projects. I do hope that the situation will improve once the "big rewrite" with a WASM backend is done.
I don't think hotels can do this, either the hotels don't know how to claim the business back, or this is a part of their agreement.
Yeah, as I talked about in both the original blog post and my parent comment, we've specifically designed Redux Toolkit to eliminate the "incidental complexity" that came along with using Redux [0]:

- Immer makes writing immutable updates easy, because you can write "mutating" logic like `state.todos[5].completed = true`

- `configureStore` sets up a Redux store with good defaults (DevTools extension, thunks, mutation checking) in a single line of code and has easier-to-read options if you do need to tweak the config

- `createSlice` eliminates the need to write any action creators or action types by hand

- Our new `createAsyncThunk` and `createEntityAdapter` APIs (new in v1.3.0 [1]) simplify the common use cases of dispatching actions as part of data fetching and managing normalized data in your state

Also, RTK is written in TypeScript, and designed to infer as much as possible. For example, if you declare the type of the action payload in a `createSlice` reducer, the generated action creator has its payload argument typed automatically to match.

Meanwhile, the React-Redux hooks API generally requires less code than `connect` does, and is easier to use with TypeScript as well.

Finally, we're now encouraging folks to use the "ducks" pattern for single-file Redux logic [2], which cuts down the number of files you might have to work on for a given feature, and using `createSlice` basically gives you ducks files for free [3].

[0] https://blog.isquaredsoftware.com/2019/10/redux-starter-kit-...

[1] https://github.com/reduxjs/redux-toolkit/releases/tag/v1.3.0

[2] https://redux.js.org/style-guide/style-guide#structure-files...

[3] https://redux-toolkit.js.org/usage/usage-guide#exporting-and...
Remember when the women of Twin Peaks made nostalgia new again?
IIRC, Lattner's the only interviewee, and this was his second appearance.
> if you take a 0.3% chance every day, you'll land it once a year.

"actualllyyy" you've got a 2 in 3 chance of landing it each year.

1-((1-(0.3/100))^365) = 0.66

EDIT: stop upvoting me, he's right. The question isn't "what is the probability of at least one success in a year", but rather "how many trials, on average, does it take to get one success" - and the answer to THAT is in fact 333, from the geometric distribution.
GPL+Commercial requires copyright assignment, which is a pretty sure way to turn off potential contributors. I mean, if you don't want to contribute to BSD-style licensed projects because you don't want others to leech without giving anything back, how on earth could you simultaneously be ok with assigning your copyright to some (sleezy/evil/you name it) corporation?

And no, I don't really have an answer either. Successful open source business models are few and far between. Redhat is perhaps the one big example of a (very) successful open source company.

To some extent I think the worry about leeching is something which can be addressed with culture as well as licenses. Plenty of successful BSD/apache licensed projects around, including with largely corporate contributors, because they understand the long-term value from contributing to the common pool rather than forking and trying to sell "proprietary enhanced" versions.
Singapore open-sources its contact tracing app
Maybe "by the type system" was the wrong way to say that. What I meant is that if I wanted to write my own Result, say Result2, it wouldn't be included in the question mark syntax. Perhaps I could write a macro for it, I guess, but the real one is not implemented as a macro and if I wanted to go use my knowledge of the language fundamentals to read the standard library and figure out what it does, I couldn't do that. It just is that way.
> I think it will translate to extremely fast web services in practice.

In practice, it's probably not going to matter all that much because the average web service does way more time-expensive things like disk IO or SQL queries. The more significant effect is that async-await being really really fast enables you to use it in more places. For example, if you have a tight computation loop where different aspects of the logic are meshed together in a hard-to-read way, now you could try detangling it into several async actors talking to each other to make it more readable, without utterly destroying the performance characteristics.
IntelliJ Idea LightEdit Mode
Yes but not the point of parent comment.
Can Drugs Help Us Focus?
Having used both Ant and Material UI on mid-sized React projects I can say that MUI has much better documentation and flexibility, at a slight cost of having to grok their styling convention. Once you get that it's smooth sailing, with a fairly active community, a lot of intuitive components and generally hassle-free dev experience. Ant was a bit more of a struggle, personally, with less clarity in the docs and a less active (English-speaking at least) community.
It's not safe to process untrusted files with 7zip

https://news.ycombinator.com/item?id=16985460