skysight-inc/HackerNews huggingface dataset:
Programming tools should work this way because we write code; config files are effectively code that doesn't execute (or sometimes does.) A lot of the config files we use (think stuff like: gitignore, eslint/babel configuration, Dockerfiles, package.toml, etc.) we version into source control so that we can track changes over time. I can't think of a good UI that would make editing these files better; VSCode probably has done the best by providing autocompletion in YAML and JSON files using JSONSchema.

Text files aren't perfect, but they're hard to beat. It's not like the hardest part of programming is actually syntax, anyways. You can always improve on this by providing better assisted editing.

If there's anything I'd actually want it would be for software to have pluggable configuration so I can instruct it to pull its configuration from a database or something along those lines.

edit: and on that note, it’s probably the command line interface that actually would strongly benefit from some consideration. CLI arguments are currently a flat unstructured list... but almost everything at least has key value pairs.
Brilliant to see where some land masses stay relatively intact and how little they've changed. Newfoundland and Labrador in today's Eastern Canada stand out to me. I really want to those weathered ancient mountains some day.
That’s not the same though. The sunglasses are in front of my eyes. If you put that mesh on my retina, I’m gonna see lines (if by some miracle my eyes still work)
The problem is why should people be "converting the mess" in the first place. Backward compatibility, especially when it comes to programming languages, should be a given. If anything, this is reason that people should stop using python.
Gives the term _shellcode_ a whole new meaning!
Is there any demand for that? I mean in 2020 you are one docker command away from having an automatically refreshing tls server ready and serving.
It is not uncommon to have multiple employers and be an employee at all of them. Someone might work one shift at CVS, then another at Rite Aid. Someone might work at Wendy's one day and work at McDonald's the next.
Do you think it would be a better use of time and resources to find each and every single market that is subjectively not sufficiently competitive and break up the participants/introduce new participants -- or create some blanket rules that stop people from being taken advantage of (up to and including UBI and socialized medicine)? Why let anyone fall through the cracks?
I don't think that's quite fair. Irreproducible papers have supposedly gone through a fairly rigorous review process by their peers, and are usually published by someone with a PhD (or who will soon have one) at an institution of higher learning. Many papers (which often end up being irreproducible) use language that says "This is the thing I found, and it is/is not true."

OSS is often someone learning, or who has an itch to scratch, and put some code out there that may or may not solve your problem or work right. The "lack of warranty" clause in most open-source licensing is really important here, because it's largely designed to say "hey, I did a thing but make no guarantees so use at your own risk", whereas a published paper says "hey, a number of experts and people who should know all agree that this is a thoroughly-researched and well-thought-out position, and you can probably consider it to be true (or nearly so) and base some of your decisions on it." I think that change in context is really important to consider when making the analogy here.
I don't know what's more horrifying - how old that made me feel or that pet cloning is a thing. Marketwatch says it costs something like $50,000.

Of course there's been discussions on HN about it! [1][2]

[1] https://news.ycombinator.com/item?id=17723325

[2] https://news.ycombinator.com/item?id=16506712
Also, Regression and Other Stories is the new edition of the Regression with Multilevel models book, and it's much, much better (especially for n00bs).
Thanks for another cool article! This one has a lot of meat so it will take some time to go through it.

One question, how useful are the patents linked to in the footnotes for your work? (I hesitate to even ask this in fear of stirring yet another patent flame war.)

P.S. Do you have a patreon, or equivalent, page? If not, you really need one. I would happily subscribe.
Shorting serves a valuable purpose. It removes capital from the hands of people stupid enough to believe fraudsters, and reallocates it to people who dont. The whole purpose of markets is to facilitate the efficient allocation of capital, and shorting is clearly an important part of that.
A large thread about 1.0 from a few months ago: https://news.ycombinator.com/item?id=23172483
Companies will simply leave California.
My toughts:

2. Yes, in areas where other governments profit isnt your loss. I think there are lots of these. For example, if you have software which makes people more healthy, you wont lose if people in other countries get healthier as well.

3. Yes, similarly in many areas others auditing the software is harmless.
Any experience embedding deno in a c++ application? I absolutely lovehow seamlessly lua integrates into my code, but I just find the language itself absolutely unpleasant to work with.
The Permian Extinction–When Life Nearly Came to an End
How would this work for a condo or apartment type property? If just one of the unit wants blur, does the whole building get blurred?
Also, what happens if that person moves?
Well, first you need to decide if it's worth caring about that, because in order to deal with it you have to impose restrictions beyond redistribution, which means your license is no longer a pure copyright license, which arguably means it violates Freedom Zero and cannot qualify as a Free Software license per the FSF's own definition (of course they say the AGPL does, as it's their own license, but by a strict reading, it doesn't; by a looser reading it does, but it is also toothless). (It would qualify as open source under the OSI definition, but the OSI definition is unfortunately really poor in this regard, as it does not require lack of usage restrictions; you could say "you can't run my app on more than one CPU core or have more than 4 simultaneous users" and that license would still meet the OSI guidelines!)

Now, if you're prepared to make that concession... I don't know what to tell you. The AGPL is a terrible option as I've mentioned. However, the FSF deliberately made the GPLv3 and AGPLv3 an interoperable pair, so if you want to link with GPLed software, you have no other option. If you don't have any GPLed dependencies, you could write your own license, and properly spell out what "remote network interaction" means for your app (and especially how transitive it is to being integrated into other systems, interaction with proxies, frontends, etc - all of which the AGPL is completely mute on), and how the source should be distributed. Ideally you'd build in a source code offer mechanism into your network protocol and make the app able to serve its own source code, so as to not burden your users with licensing traps they have to take explicit action on, and then make the licensing conditional on that.

In principle, since you can always make a license less strict via exceptions, if you're willing to accept that the AGPL may be completely ineffective at closing the loophole depending on interpretation, then you could use the AGPL and spell out what the required extent of the network interaction requirements is in the form of an exception; this would lessen the problematic burden of the AGPL on your users, but it doesn't buy you any extra protections, as you can only go weaker, not stronger.
First of all, I want to point out that some parts you "quoted" in your answer were not written by me. It is quite a bit irritating how this appears.

And while the oldest plants were switched off after Fukushima, Germany didn't just "switch off" the nuclear production. The nuclear contribution to the electricity production gradually declined from 19% of all electricity in 2011 to 12% in 2020 so far. The next years should bring a steeper decline though, as more plants get phased out.
I would like to also add if your curious about more modern FPGA bit-streams there are these two projects which reverse-engineered bit streams for open source synthesis.

https://github.com/SymbiFlow/prjxray
https://github.com/SymbiFlow/icestorm
I just started digging into it a few hours back, so I can't give you a concrete answer. A hello world example for the deno_core to give an idea on how the Ops and ResourceIds should be used. The examples given are not really clear at a glance what they are doing and I had to read through a few of the test cases before I got some idea how JsRuntime should work.
> Hey Google, why not shutdown location and frequent play service updates as they aren't helping my phone battery either

Doesn’t mention GPS. That may be what the author meant, but certainly could be written far clearer.

Still, Google isn’t using GPS all the time, their power management strategy can’t allow that. It’s likely only using it when its deemed necessary. Android is tuned to balance offer users the most functionality possible with longest battery life. If it did not iOS would destroy it in battery life tests.

Triangulation is necessary to determine which tower to connect to and when to switch to a new tower. It’s why they are called “cellular” phones.
If a "backup" is made of your brain before you died, and it's restored afterwards to a new body, wouldn't that new copy be totally disconnected from the original. The brain in the new body might behave identically to the original, but the entity (or "soul", for lack of a better word) experiencing it won't be the original. This is trivially demonstrated by using the same backup process to make a clone (ie. restoring the backup but not killing the original). Clearly you won't be having the experiences of both bodies, would you?

https://en.wikipedia.org/wiki/Teletransportation_paradox
As if all those shell scripts are portable across time and distributions. Or PHP code. Or really any other code. How many builds of your software are truly reproducible?

Python 2/3 incompatibility is always magnified for some reason, but it's nothing out of the ordinary in my experience.

Didn't we just recently have a highly upvoted/heavily debated HN submission on semver? Enough said...
What’s the killer feature that will lead to node developers switching over in droves?
The encryption has been broken. You can read about it here https://news.ycombinator.com/item?id=22915831
> Doing something because other people are doing it is the path to misery and competition.

So very very wrong.

Doing everything everyone else is doing is the road to group membership and social acceptance and great cultural fit and the best jobs and the most lucrative opportunities and loads and loads of money.

Doing things specifically because nobody else is doing them is a ticket to a pit of despair full of poverty and loneliness and isolation.

I know the difference very well because I never do popular things. I always choose unpopular projects that nobody cares about because my attitude is if a project is too popular then too many people are doing it already. I want to do things that nobody else is doing because if not me then nobody else will do them.

Doing something that nobody else is doing is very rewarding. Talking to other people about it is misery. People do not care and you are competing for their attention with other things that they actually care about. And you lose the competition.
I gave Deno a try last night.

There seemed to be some few alternatives to work with databases but I would like to see some more maturity before using this on production.
> it seems like Apple took a couple hundred really good UI engineers and threw them at this

Like all Apple efforts it was crafted by a small, tight knit cross-functional group of stellar engineers.
Lifeline-rs, a dependency injection library for async applications
It takes guts to go for such a stretched auditory pun via text, kudos to you
Hm it looks like it would satisfy a lot of binary data use cases, but so would MessagePack, CBOR, and probably a few dozen other formats.

A design goal of QSN is to be human readable like JSON. You can view it at the terminal, in an editor, in an e-mail, or in the browser. IMO that fits more naturally with Unix and the web.

So I guess I should make clear that it's not only about "binary data", but it's that + a few other constraints.
LMAO 8:10 Interviewer: This seems to me first and foremost to be a technology looking for a problem to solve
Access Movies and TV Shows for Free
It is a (short term) self enforcing principle, that is the pitty.
Like in other ideologies.
Civilization should mitigate such effects.
And in some cases suceeded.
So progress might be possible and should be thought of.
But not in changing people or the "nature" of people.
There has been progress in history (also backfalls).
We would not have warm houses or water supply or electricity if someone had not believed in making a better life.
This is exactly what happened to Common Core.
I would think that the challenge is to find good recommenders rather than specific recommendations.

If I can find similar tastes, maybe a little bit different, then that will result in good recommendations.

So I would want to find people who both like similar things but also dislike similar things. It will be interesting to find people my similarity and see which are best at finding books I like.
> but that's a known fact and has very little to do with any specific vendor.

Yet I can still run Windows 10 on a computer that I've had in my closet for the last 15 years.
Since its taxpayers money, any custom made software for gov MUST be FOSS or we can equally abandon any logic whatsoever - citizens payed for it, gov employees were working with implementation team on shaping it, so it belongs to them. This doesn't have to be so for supportive domains such as databases but I would personally prefer that also (i.e. Postgresql instead Oracle db).

There are many more reasons for this then mentioned, including keeping more IT experts locally, better connections with academia, higher salaries for gov IT guys, less corruption etc.

The MAJOR thing is actually that gov companies and their systems are usually quite complex and not something that can be easily (or at all) correctly done by external team of any kind - you need to be there, on the spot, and live that system for years to know how to program it, improve it, and make it good for the country and its citizens. I worked for gov 15 years, and did many huge projects with various companies - IBM, Microsoft, Oracle, Cisco etc... almost all being complete garbage, especially for the usual multi billion price that is payed to those corps yearly. There is an illusion that big names mean big and qualified team, good responsibility delegation (there is the 'nobody got fired for choosing IBM' thing) and that high price means quality, but in practice it never works like that, reality is quite the opposite (except responsibility delegation/dispersion which is totally true).

The major reason that proprietary software is so prominent in gov is corruption.
Sorry, I was too consumed by making a clear statements and didn't put enough effort into arguments.

First of all, I am talking about teams of 20+ employees, e.g. 3 pizz-teams or more. This is a number when you definitely need two levels of management, event if one of them consists of makers-managers, e.g. teamleads.

That is the scale where you can't keep all the data in one head. So the information is distributed among employees, managers and no one has a full pucture. Some people know their segments with specifics, some has a helicopter view with coarse details.

Now, in office-based team you have a privilege to keep most of the data in the heads, because everyone can just walk to anyone and talk to them at the end of the day (pun intended).

You have those daily stand-ups, weekly all-hands, but most of the data are still don't have a hard copies. Of course you are writing specs, maybe you are writing docs, chances are you are writing company-wide weekly updates (and wondering if anyone actually reading it).

I know a lot of companies where people just changed in-person meetings to Zoom and are thinking they are fully remote now, In fact, they are just burning through data savings in their employees heads. It becomes visible rignt about now, after about 6 months of this quasi-remote. Teams are slowly turning into mess where right hand has no idea about left one. What took couple of weeks now takes month or even longer.

So, managers are trying to fight it with more conference-calling, more reporting, itemized plans and Gant diagrams, putting some pressure to engineers. At the same time engineers are trying to restore horisontal communications via chats, which leads to distraction and further loss of productivity.

This is because remote teams should work in a completely different manner. Great example is Gitlab, check out their handbook [0]. Mind you - that this is just a tip of the iceberg, they are incredibly transparent, but they are showing less than 5% of what they have.

So, in fully remote company you should organize all processes and workflows in a manner when no one should be synchronized with anyone in real time. You should ditch conference-calling almost entirely and record remaining video meetings to be available later. You should switch from chats back to emails, yes! You have to write down everything: specs, docs, meeting protocols, decisions - both accepted and rejected. And this is just a beginning: you also should keep all those in an actual state. Do you know a lot of companies where documentation and code are 100% coherent 100% of the time? I don't.

And of course most of this work is falling onto managers' shoulders: not only writing stuff by themselves, but checking that everyone else is writing stuff too.

Some people (even in this thread) may say that their company is doing just fine without all this and they are just happy saving commuting time. But I am sure they are just being ineffective, which means sooner or later they will be predated by more effective competitors.

[0] https://about.gitlab.com/handbook/
The neighbor got divorced because they discovered their spouse’s infidelity. The unusual method of discovery is incidental.
Most of the points make sense, but this one does not

> Impact on the body - prolonged unmoderated sitting in bad postures, eye strain due to constant staring into the screen, bad eating habits, etc.

How does WFH change how you sit and the eye strain? You’re doing the same work, what changed? IMO having a good office setup (chair, device, screen, room lighting) is a must for any WFH position, but especially if it’s full-time.

Also for me, the food is better because in the office I used to eat snacks and go out in restaurants or fast foods. Now I mostly make food at home, and with the benefit of s garden have home-grown vegetables. So I eat better and spend less, plus I cut down the crap food from couple times a week to a few times in a month.

As I see it, the argument 4) applies only with refusing to invest into a proper working environment setup and with the lack of discipline. But I hardly believe someone with the lack of discipline would eat any better in the office. And I’m taking this from my past experience.
Yeah, but all those tools by default don't print anything if they run successfully, which is indistinguishable from silent failure.

If you look at all modern tools, this approach has been abandoned, especially for long running operations, since it's obviously bad UX.
They are worse, lithium batteries tend to explode or catch fire. Cool description, I've never noticed these tendrils you describe.
And yet so many people refuse to read working code, and agitate for re-writes.

It's just bizarre to me.
Sounds like a case of a sticky wheel gets the grease. If it became such an issue it threatened the viability of street view, they'd quickly come up with a policy to deal with it. As is its not worth the time to create or administer the ongoing ops such a policy would require.
The Owosso Pulse: Michigan's 'Back to the Future' Autocycle
Bisqwit has some videos that are definitely worth checking out as well. I really enjoyed his NES memory visualizations: https://youtube.com/watch?v=hqDGWfZhitc
One thing I am a bit upset is how Apple approaches SwiftUI / Combine, as these two to me, are foundational pieces to the Swift language ecosystem. Particularly:

1. There is no way to bundle SwiftUI / Combine to the app so you can ship to earlier iOS versions, making development exclusively done on newer OS version. More over, for any bug fixes on SwiftUI / Combine, you have to wait for the OS updates for the fix. Just updating your Xcode is not enough.

2. While the SwiftUI required language features are all upstreamed to Swift language, and core developers have been patient to articulate why. If SwiftUI / Combine development was done in public (i.e. open-source), bug-fixes and language improvements will be much smoother.

To Apple, point 2 probably is a big leap. But they've done Swift open-source release, and it works relatively well with a sizeable open-source ecosystem on other platforms now.
wxWidgets uses native widgets on macOS.
Foundersnetwork.com has a few. If you need an invite let me know.
Writing multi-package analysis tools for Go
Convex Algorithms
I wish the author had provided more in the way of examples to ground his points. This is a broad topic that could manifest itself in different ways, some of which are more and less applicable. For example:

- Ads with claims like "This single mom makes $$$ working from home, you can too!"

- Clickbait news titles. (You could define "clickbait" here as the most egregious, or as the sensational nature of headlines across the industry.

- More subtle, but pervasive trends manipulation like $_.99 price tags, or arranging grocery stores not for customer convenience, but to encourage them to buy more things

- Even more subtle: The ubiquitous practice of advertising (Perhaps on a product webpage) the positive qualities upfront without mentioning the drawbacks or competition. Is that disrespectful, or just good business practice?

- Video games puzzles designed to be easy to solve. Eg I could paraphrase some of the Portal levels with dev commentary as "We wanted to make this more challenging, but our playtesters kept getting confused, so we made the solution obvious."

- Junk food manufacturers micromanaging the sugar etc content to keep the user hooked and get just the right amount of good-feelings flowing.

- Restaurants loading every dish with salt.

Does the article apply to all these? Maybe? They're on a spectrum, with some more clear-cut as disrespectful than others.
There are plenty of videos of Orcas and other dolphins playing in the wild. I don't think they're generally on a super tight caloric budget.
Ecma-402 support (the 'Intl' object, locale dependent number and date formatting, etc.) requires linking with the ICU library.

We expect to support that in a future release.