skysight-inc/HackerNews huggingface dataset:
>We don't have to use anecdotes, we have data.

Why should I trust the data?

There have been too many times of selective definitions, selective measurements, selective polling, selective measurements... all for reaching an agreed upon conclusion. For example, the CDC used a specific definition of rape (excluding forced penetration, counting it as general sexual assault instead) that excluded the majority of male victims of domestic rape, and then used the now biased results to give high level summary data that was greatly misleading.

If I can't trust the CDC's reporting on an issues as serious as domestic sexual violence, then how can I trust anyone's data? Maybe peer reviewed science in the hard sciences, but social science (including economics) has a similar issue of selective measurements, ignored replication, and biased publishing.

So I guess to start with, what peer review has this undergone? To what extent has it been replicated? What criticisms does it have (and none is a very bad sign)? What is the biases of the group(s) that did the work involved? What is the biases of the group(s) that provided funding?

Yes, it is odd I'm at the point where anecdotes seem to have as much weight as data because anecdotes are understood to be inherently biased whereas data is treated as pure, reliable, and free of bias when it isn't.

Also, please note that someone has already posted a criticism of this data.
So I use QuickCheck often and I'm a true believer, but the point this post is making is absolutely justified. Tying the test generation to the type is often requires some creative ways of writing `Arbitrary` instances (the specification of how test cases should be generated).

However, I don't think what the author is suggesting in its place better. The advantage of tying the test case generation to the type is that it's compositional. Lots of sub Arbitrary instances come together to generate the test case and in the long term I find this to be more maintainable. Whereas the author's approach discourages compositionally.

The real problem is that the types in vanilla Haskell are too loose, so there lots of inhabitants of a type that we are not interested in. The author mentions in passing, dependent-types might be a solution and that is exactly right. What is needed is to make the irrelevant terms illegal altogether. This is pretty achievable and is already somewhat used. For example, the program synthesis (proof search) mechanism of Idris 2[0] uses linear[1] dependent types[2] to heavily constrain which terms are possible candidates for a given type. The specificity of the type reduces the search space, hence increases the effectiveness of the proof search.

[0] https://github.com/edwinb/Idris2

[1] https://en.wikipedia.org/wiki/Substructural_type_system#Line...

[2] https://en.wikipedia.org/wiki/Dependent_type
I guess I just accept es5 for the necessary evil it is.

i'm not sold on the orm approaches.

typescript, reason, svelte, etc, all bring interesting ideas to the table.

end of the day, you can probably eliminate a lot of cruft from your ui before actually being required to resort to these things. I still include tag mithril.min.js and stuff like that plenty, and the world didn't stop nor did I die writing hyperscript. or js. or html. or sql. or whatever...
Thank you. Somehow is cool this days to write non-sense in tech forums. The Kurds are also a large ethnic group in Turkey, so is the author of Notepad++ will be adding a mention to them in the next release note? Native Americans in the US and Canada? Buryats in Russia? and the list goes on and on... but hey, I guess is too hard to do a little research before pretending to be cool.
You post bunch of lies / outdated statements that are not true anymore (that are super easy to find and whole community have been raving about them for last few months, so your motivations look a bit shady to be polite), and when all of them are debunked you start claiming that your preferred corporate shops don't build PCs with AMD. What kind of argument for CPU performance is that?

Go buy whatever you can even if its subpar these days, nobody else cares, but currently most performance is with AMD. Power per dollar in high performance is purely with AMD.
The people who use Linux are the ones for whom Linux does what they need. So would current Linux users be willing to pay? Probably not. But...if there was a Linux ecosystem with nice paid apps, Linux users would be the ones using nice paid apps. There's an assumption behind your question that we're assigned randomly to the OS.

In case you're wondering whether that would really happen, Android is evidence that it works. The underlying OS is irrelevant.
And yet you can’t give examples of the relevant facts that are in the NYer but not the Resgister (style of CEO’s jacket doesn’t count).

I know people have different preferences. But beliefs —about which articles lead to productive discussions — can be confused. No one is spending the hour to read this before commenting. Expecting that is a bad idea.
Sometimes a lower value is better and sometimes a higher value is better depending on the benchmark, but the ordering is always the same.

The worst one is at the top and the best one at the bottom.
Isn't moon dust mostly bauxite? (oxidized aluminum)
How will the heat dissipate if there's nowhere for it to go?
Amazon Replaces “Reviews” with “Ratings”
The general rule is that a project shouldn't need a code of conduct. A code of conduct outlines basic decency rules in which case, if it gets to the point that the project needs to be explicit about them to keep a good ambiance, that project has deeper seated issues.

Codes of conduct are great when the etiquette is ambiguous. Open source projects are not one of those.

When the users are in the wrong, you should be able to kick them out uncontroversially. And when the maintainers are in the wrong... They tend to ignore their own CoC anyway. Speaking from experience, I've tried contributing to a particular PSF project in the past, adding a feature to support a use case the maintainer did not like (supporting tab indent option in a code formatter), which was ignored and closed; and when I pointed out to the maintainer that his behaviour was in breach of the CoC, that too was ignored. What are you gonna do? In the end I had to fork the project.
I regret never making a screen snapshot myself, so probably not. I fear that Oracle is keeping XBugTool in reserve as kind of a doomsday weapon to deploy on unsuspecting customers they suspect of disloyalty, to prevent them from ever filing bugs against any Oracle software.

One thing I did keep a screen snapshot of was of how XCalc loses its shit after you resize it a bunch of times.

http://www.art.net/~hopkins/Don/unix-haters/x-windows/XCalc....
I feel crystal clear about the state and logics but missing typescript support bring me to stencil for now.

Keeping an eye on it's development.
>small and family owned businesses are absolutely hurting

likely because profit = revenue - expenses and expenses (in the form of wages) have gone up more than revenue.

Raising the minimum wage has always been bad for margins. That's why those restaurants (and economists indirectly on their payroll) try to convince us that it's bad for workers too.
Search is a perpetual battle between the ranker and the content servers trying to game it. I'd agree that over the last two years the 'SEO' gamers have been outplaying Google.
Hah, I was too quick to doubt myself.
There is also a NSA center in that area
On the flip side, I have written things that got significantly more attention that I had expected and probably came across to the project maintainers as hating on their work–and that is with multiple drafts to make it clear that this wasn't my intention. There might be random people who like to persecute individuals and their work for no good reason, but even harder to deal with are the people who have been invested in the project before and you've made unhappy; doubly so if you've reached the point where you're not interested in having certain conversations and your governance structure makes it difficult for them to feel heard. Really, this is not a simple problem and I think it's more nuanced than "people will take your Code of Conduct and use it to nitpick you and call your work stupid on the internet", when there's a whole spectrum of "this maintainer has been closing all conversations of a contentious topic by citing the governance structure" to "we made an unpopular but necessary decision that we did not explain well enough and that's causing everyone to come out of the woodwork to harass us".
Why is $15/hr the magic number? Just because it's some round number?

If raising the minimum wage has had nothing but positive effects, why not raise it to $20/hr - or some other number calculated for maximum benefit - who knows what that would be?
That's an interesting fact about Elm I wasn't especially aware of. Maybe I should have a closer look at it, even though web front-end stuff is not my cup of tea.
Like git-secrets? It’s mentioned on the site.
Yes, I would pay (and have done so in the past). Much as I'm willing to pay for good apps on my phone, even though there are plenty of free alternatives.
VS Code has really good support for editing over SSH built into a preview extension now [0]. It is as seamless as running vim over ssh, except it’s a GUI app running locally connected to a temporary VS Code server on the remote. It even supports extensions installed on the remote. I’ve tried so many different implementations to get Sublime working in this config (like SSH forwarding a samba share) and they’re all terrible compared to VS Code’s.

[0] https://code.visualstudio.com/docs/remote/remote-overview
yes. We already pay for jetbrains.

People would pay a lot for:
1. SQL ide
2. audio authoring
3. Sketch
4. Photoshop

Be warned though that the trend is for this kind of stuff to move to the web. Figma is a great example. Instead of trying to create a desktop client for Linux, they did some real complex stuff on WebAssembly and built a spectacular web client - https://www.figma.com/blog/webassembly-cut-figmas-load-time-... and https://www.figma.com/blog/how-we-built-the-figma-plugin-sys...

Figma is paid (and makes a lot of money)
Yes I would purchase something that solves an issue I am facing.

I think the lack of a standard way of doing things hurt for-profit development rather than the resistance to pay. For example, it is hard enough to make an application work well with one DE and in Linux there is plenty.

That is why I believe web apps such as VSCode, Discord etc are the saviour for linux desktop. With that, creating a cross platform environment is rather easy.
My experience doesn't match that. ISP DNS servers just return the A or AAAA record that they're asked for, and the return time is more or less identical for the two, not 4x longer.

All of the client resolvers I've ever used wait for both records to come back, and your DNS resolution returns both sets of addresses. I think OSX does some sort of racing here, but it still gives v6 some amount of head start (~150ms?).

Also, Google's published v6 stats say that 29% of their users reach them over v6. That doesn't seem to match with "you're almost always going to end up getting its ipv4 address".
of course, the ultimate loop is simply to use some barely-functioning type-inferred js to c++ driver to emscripten to webasm. that should satisfy the minimalist simple-life cravings of node devs.
Site Search, Powered by Google Search Engine
Americans are dead-set against having a working national ID system. There are even people who are upset about the mere existence of the SSN for weird religious reasons. The British situation is even worse - proof of right of residence is required for opening a bank account, working, or renting a home, but only immigrants are made to have ID cards. Also utility bills are a valid proof of address for some reason.

No, the real problem is a liability one; loan companies should be held liable for each instance of fraud where they pursue the wrong person.
That's perhaps the least dangerous of the bicycle maneuvers. Its the dashing from lane to lane, from street to sidewalk and back, into and out of blind spots unexpectedly that makes bicycles a hazard to themselves.
As a former service worker, I'd argue that cutting employee hours was exactly the goal.

Typically, in a restaurant in Philly or places with similarly lower-than-minimum service wages (which still has the $2.75 or whatever minimum for service workers), you'll be scheduled excessively for hours when the restaurant definitely isn't going to have any business. For example, coming in at 330/4 to start prep for the dinner shift.

When labor costs basically nothing, there's no reason not to overschedule them.

This reduced the amount of time I could spend outside of work learning to program (for example... since it's what I did hah) or others could spend improving their skills for basically no money. It's a huge detriment to the employees. You'd stand around cleaning for some nitpicky manager making 0/hour effectively, doing untipped cleaning and prep work. Your paychecks will be $0 if you get even a modest amount of tips for the night (it's all taxed).

Now restaurants will be more particular about how they schedule employees, and the untipped work actually costs money to have done (if a janitor would have to be paid minimum+ to do it, why should a server do it for $2.75/hr)?
Can you explain what you mean by this? I have never heard the term "documentation theater", yet it seems like you're using it pejoratively here. The Microsoft version has a summary of the intended purpose of the class, a brief code snippet showing what its use might look like, images demonstrating the output of using the class, and lists of all available constructors, properties, and methods along with a brief description of each. If this is "documentation theater", please sign me up for more.
"beautifully designed", "good looking", and "easy to use" are three very different things.

"Beautifully designed" is not important to most users unless they get the source code and need to make changes or enhancements.

"Good looking" is nice, but hard to define depending on what kind of application it is, especially on Linux. What does it mean for a server daemon to be "good looking"? What does it mean for a command line tool to be "good looking"?

"Easy to use" is very important to most users, but is also rather subjective depending on individual user preferences and experience level. For example, I think vim and emacs are both "easy to use" because I have years of experience using both for various tasks. YMMV.

Most users value utility, "easy to use", and "good price" when it comes to paid software:

1) Utility is essential because if the sofware is not useful then what is it good for?

2) "Easy to use" is important, but subjective. Know your intended audience and design to meet their needs. Seek user feedback early and often to tailor your design to match the user's expected ideas of "easy to use".

3) "Good price" varies based on the user expectation and the value proposition that you offer. If the software is extremely useful (high utility) and easy enough to use, users will pay for it.

Ask yourself "What does my software offer that is worth paying for?"
Building codes have already made it so safe for the masses that fire departments often have a tough time justifying their own existence.

Everyone is already doing basic mitigation unless they are breaking the law.
It certainly is both. China's rationale is that their current capitalistic phase is a glorified long-term NEP (Lenin's capitalistic phase for the USSR). They claim to be doing this to build up their economy to first world levels before progressing to the next phase of socialism in accordance with Marxian progression of economic structures. The problem communist countries have faced is not being able to live up to first world levels and both superpowers, the USSR and China, decided that reverting to capitalism is the answer.

Of course, this isn't left 100% to the free market so the state has overall planned control of the economy and will intervene to preserve their interpretation of socialism ("socialism with Chinese characteristics").
I actually have an Economics degree, so I guess I'm qualified.
I'd prefer a well-designed (not necessarily pretty) cross-platform application. Not so much because I think the Linux version would be unsustainable, but because I'm an OS polyglot. The Jetbrains editors are a good example of this.

Cross-platform electron apps would also apply, but generally I'd prefer more native applications, just for performance reasons.
By moving from a non-Latin script to a Latin script, you destroy puns, and I feel that destroys the culture, too. It is too big a price to pay.
As someone who has bought applications for Mac and iOS, and also donates to FOSS projects, I would certainly buy software applications on Linux if they looked better and had a good user experience. I really don’t want to deal with hand editing config files and running shell commands to get things to work, because while I can do those, I cannot have a sustainable system I can pass on to others who’re just non-technical common users of software.

I think Linux itself, and many applications on it, don’t look great because the developers behind those are highly technical and ideological people who can, and do, cater to other technical and ideological people. They seem to think of UI and UX as wasteful things over mere, and many a times complex, functionality (they probably also believe they’re good designers who don’t need help from UI/UX experts). Even larger projects don’t spend enough time or money to use better fonts, design better layouts, use nicer color schemes, design better user experiences, etc. (one glaring example of this is LibreOffice).

Stepping outside Linux while remaining on free software, Matrix is spending time and money on improving UX because the people behind it realize the importance of it. Within the Linux world, the attitude seems to be more of users being expected to qualify to use the system - “the users are capable and will figure it out” seems to be the background thinking.

Distributions like ElementaryOS have tried to charge (or accept, depending on how you see the website) money for more beautifully designed systems than you could get out of the box elsewhere. If larger companies take such an approach or even adopt some of the niceties from such distributions, the Linux world would be much better off.
> I would love to have an example of what exactly he is writing about.

Thank you. This such a nothing article with a clickbait headline.
This reminds me of my early C days dilemma: "Check for a disallowed NULL pointer argument on function entry or just trust that it will have a valid value?" And a mixed feeling that would settle after putting an assert there.

Eventually, one develops a "pragmatic trust", appropriate to the level of interactions in the code.

After all a state change is a kind of input resulting from an interaction. Some interactions are more trusted than others.

Asserting reality after every handshake is not going to make one feeling safer. Operating in a trusted environment and understanding and upholding its premises does add one more member to enforce that "safety in [sane] numbers".
> It may be partially that English is really foreign for us, while it's pretty close linguistically to Swedish, both being Germanic.

That wouldn't explain it, because we do the same in Dutch: just leave off the diacritics. Diacritics are pretty rare in Dutch, though.
The Drivers of Social Preferences: Evidence from a Nationwide Tipping Experiment [pdf]
Well, I know that it supports exporting to custom elements, what I miss is the option to NOT use shadow DOM (now it is forced)
You only get a limited number of free hours. 1000 with a credit card otherwise 550.

https://www.heroku.com/free
True businesses? Company towns?

There is a reason they don't exist anymore. They were the quickiest to build but did not survive a downturn most closed up shop after the mine was closed.

Towns built with various piblic/private spaces/businesses can survive one part of the economy doing poorly.

Don't pine for a made in China solution until you could actually live one. If you were in that situation (the average Chinese factory worker) now you wouldn't be on the internet writing this you would be working your 7 day 16 hour shift.
Notepad++ has a bit of a history in releasing versions in support of various campaigns, ranging from a "Je suis Charlie" edition to a "Tiananmen June Fourth Incident" edition.

I remember one edition included an auto-typing feature, where a new tab would be opened, and content start typing into it, which frankly was quite alarming for an update of a piece of software that you've been using for a while...
I agree with your observation, except for the part where he not bashing on QuickCheck (he is, but you have to click the first link in the article in order to find it).

> One of the big differences between Hypothesis and Haskell QuickCheck is how shrinking is handled.

> Specifically, the way shrinking is handled in Haskell QuickCheck is bad and the way it works in Hypothesis (and also in test.check and EQC) is good. If you’re implementing a property based testing system, you should use the good way. If you’re using a property based testing system and it doesn’t use the good way, you need to know about this failure mode.

> The big difference is whether shrinking is integrated into generation.

> Integrating shrinking into generation has two large benefits...

> The first is mostly important from a convenience point of view...

> But the second is <i>really</i> important, because the lack of it makes your test failures potentially extremely confusing.
So the author can't solve a problem, goes ahead to say that javascript is c because of one situation, then promotes rust by the end. All with a clickbait title to boot.

I'd be more angry but this type of formula for an article is used so often now that it should be expected.

I can't wait until people figure out that the individuals that aren't competent enough to handle C's issues, aren't going to be competent enough to handle Rust's either.

Hopefully the Rust hype train dies soon. There is simply too much bandwaggoning involved in this language to keep bias out of the equation when considering using it to solve a problem.
Old really means there's been more time to identify and solve the problem, and the fact it hasn't been cleanly solved is a lot more indicative of priorities than time or tech.

Microsoft and Apple have the incentive of selling to billion-user markets. The open source community, on average, appears to have demonstrated a lack of interest in opening up the user-base further (and expecting that user-base to just roll their own solution creates multiple catch-22 and tragedy of the commons problems).

Why one of the commercial open-source vendors hasn't taken this on as a core challenge, I do not know.
I would say so, the URLs are pretty darn long:

https://scontent-arn2-2.cdninstagram.com/vp/5932ec6f480e416a...

It's not obvious how likely it is to guess a valid URL, but even if it's just the first path, its still 128 bits (assuming a hexadecimal alphabet). According to [0] there are 50+ billion photos uploaded to Instagram. Even if we assume 10 000 billion posts (200x margin), 10^13 is a very small number in comparison to 2^128≈3.4*10^38,

[0]: https://www.omnicoreagency.com/instagram-statistics/

(In the the URL above I've changed one character, yielding it invalid, leaving it as an exercise for the reader to figure the missing one out.)