skysight-inc/HackerNews huggingface dataset:
I used to love epic monster board wargames in my teens. Advanced 3rd Reich was my favorite, and when played along with it's companion Empire of the Rising Sun could simulate all of WWII in about 80 hours or so - assuming you were completely familiar with about 2000 pages of rules and moving as fast as possible with little time for strategic thought. Realistically, it could run significantly longer. But still short enough that you could (and might want to) play it multiple times in a lifetime. (The current version, updated over the years, is called A World At War and lists a playtime of 48 hours.)

Some of the very detailed air and naval tactical wargames back then could take an hour or so to simulate a few seconds or minutes of combat. I tried some of those and did not particularly enjoy them, but if a computer could help... My learning to program was significantly driven by making computer-aided-wargaming assistant software. But before long, PC wargames became more playable and I started turning to them instead.

As an adult with work and family, I can't play the monsters or rivet-counters anymore. I have great memories of obsessing over them and all their details and possibilities. But even now that they're computerized, trying to fit all that information in my head, handle all the detail and micromanagement feels too much like work. Such games are works of art that provide a special place and time and some lasting memories for those who can get into them.
That's not how it works, the server wouldn't execute JS that is meant for a browser client, it would just serve it like any other static file.

What you're suggesting will actually hamper security, because scripts served from your domain have less limitations(see https://en.wikipedia.org/wiki/Same-origin_policy , https://en.wikipedia.org/wiki/Content_Security_Policy and other mechanisms)
Funny thing about AJAX is that this acronym means nothing. Asynchronous JavaScript? Well, JavaScript was always asynchronous. And XML? What does it have with XML?
The only good solution is life in prison for the CEO and the board. Fines will not work. We need to fix incentives at the top.
They are worrying about important issues (especially data sharing and the TeX-illiterate) and by dealing with them will make it harder for the entrenched journal complex to fight back.

With an orthogonal peer review mechanism (you can still upload your preprints, but third party review/peer review/editorial sites would link to solid work in their respective areas) there would be no need for the old publishers.

What we need is for the granting organizations to 1> require publication with normalized and raw data 2> require ArXiv publication and 3> fund some independent peer review organizations.
"Most web apps are built in languages that don't have buffer overrun problems."

You misunderstood the author's point. Things like SQL injection are really equivalent to buffer overflow attacks -- data creeping into the code because of poor bounds checking.
Flask is a Python framework for web servers. It's like 5 minutes to a HelloWorld webpage
Admittedly few, but generally in native land you have the ability to plaster over platform deficiencies with equally-well-performing code. On the web, you can never really compete with the execution speed or integration of the native code in the browser, so you have to accept whatever is there.

I'd say OpenSSH (since SSH2) has a better track record than most webapps, as unfair a comparison as that is. In terms of local robustness, there's SeL4, which is also a bit unfair (since it took about a decade for a team of geniuses to prove enough properties to make it probably not very buggy).
That's not an age or experience thing. People can be jerks at any age or level. Good engineers do not equate illiteracy of the codebase (unfamiliarity) with ineptitude. Good engineers educate without contempt. On the flip side, many people come into an organization questioning why or how things are done. Often, the current product is a ball of inperfection and compromises. Spend 2x more time reading the code than asking questions. Understand why a fence was put there before you tear it down.
hand sanitizers aren't to replace soap, where as soap kills and washes surviving germs away
How do two people edit a document in Windows-95-era Word?

LaunchPlan2017Q4Final4Draft1Beta.doc with Track Changes on.
YouTube+Best+Video+Downloader+2
Entirely subjective.
People always shit on C for security, perhaps rightly so. But I would like to point out that 99% of everything out there has C or C++ at its base. cpython is c, java is C++, rust is based on llvm which is C++. Yes implementing your user facing application in some non-c language may improve security, but you are still depending on C when you do so.

So is C the problem, or is it modern CPU architecture? C has stuck around for so long because of how close it is to assembly language. There will always be a need for a language that is one layer above assembly, and currently assembly is incredibly hard to secure.
Thanks!

Do you know nnir has a notmuch backend now? So one can avoid running Dovecot locally and still have great search capabilities with a mbsync+notmuch setup.
You read wrong, not 6 characters but 6 numbers. So no spaces or casing.
Parsing `ls` is never a good idea[1]. A more robust way to use globbing in a POSIX shell would be something like this:

printf "%s\0" files* | xargs -0 -n 1 -P 8 long_process

1. http://mywiki.wooledge.org/ParsingLs
You make the perfect product

You strive for excellence

You keep improving

Like Jiro did with sushi

And then the product dies with you
Project Mayhem?
Exactly. Free market would turn it into care only for the wealthy while the poor die at home.
Collecting meta-data is not benign at all, it's trivial for the usual suspects to de-anonymise, and profile based on browsing habits.

Fat protocols should marshal the true web 2.0 along with DAOs.
For the sake of creativity, suppose browsers were the wrong direction to take for web exploration. What do we do now?

The same idea may be applied to an operating system's ability to allow a user to operate on their machine.

Edit: It would be useful to consider why the need for a universal interface to the internet was originally sought out.
Correct me if I'm wrong, but I recall reading the US government gives some sort of tax benefit to the employer for providing parking spaces for employees. Some people say this subsidizes suburban sprawl. https://books.google.com/books?id=ZIqIN2j2LOUC&pg=PA82#v=one...
Aren't there laws against releasing payroll data without the consent of the employee?
This is a clever site. Nicely done!

I can't help but laugh at London's best, though: https://i.imgur.com/HWgujDq.png
It would also mean another Turing complete language embedded in browsers, in addition to… JavaScript, XSLT, GLSL (WebGL), WebAssembly, CSS itself if you squint, fonts, WebSQL (TIL some browsers still support it)… probably more I’m not thinking of.

I guess one more wouldn’t hurt.
That's true, but as I said before, I've delayed my movie timetable by 6 months, so that doesn't really affect me. Here's the thing I would have those who's job it is to design the movie theater experience understand:

If going to the cinema was free, I would still choose to wait for movies to be released for in home viewing. The cinema experience is /that/ bad.
>concurrency models

We started out with OS threads (I guess processes came first but whatever) and now we're trying to figure out what the next paradigm should be. It looks to me like it's Hoare (channels, etc) for systems programming and actors for distributed systems, both really really old ideas. To be fair there are other ideas (STM, futures, etc) that fill their own niches, but they either specialize on a smaller problem (futures) or they're still not quite ready for popular adoption (STM). If this is cyclical then I think we're pretty early in the first cycle.

Sure, the spotlight moves from one model to the other and back, but that's because the hype train cannot focus on many things at the same time, not because the ideas go out of style.
Thankfully, none of your assumptions are true if you consider TOR one part of anonymity as your parent comment did.

Not to mention, you conspicuously avoid comparing degrees of anonymity. Obviously TOR is better than SSL, which doesn't provide any anonymity.
the implication of same-origin would affect all requests made from the client. you can serve malicious js from the server all day long but it would be restricted to only talking back to that same server.
This result was not surprising, given that electric motors produce full torque from a stand, whereas ICE's have to get up in rpm before the torque gets up there.
I've never found manually keeping things in sync with the UI to be overly burdensome. I guess I've just been lucky.
If I had known I could stop all the cc spam by freezing my credit I would have done it years ago.
A standard way to at least represent common data types, dates/times, integers/longs and fixed precision decimal would be nice. I know that the JSON format doesn't specify any limit or precision limitations on the size of numeric values, but almost all libraries assume they should be read as doubles. It is a real pain for people doing analysis on semi-structured JSON after apps have been deployed for a while and the data model has evolved over time.
We don't. Learn to embrace it instead.

There's a flip side to everything. In this case, if you "fixed" this problem, it would imply a steady-state world where nothing ever changed, nothing was ever replaced, and nobody could ever take action to fix the things bugging them. To me, this is the ultimate in dystopias. It's like the world in The Giver or Tuck Everlasting, far more oppressive than the knowledge that everything we'll ever build will eventually turn to dust.

Or we could get rid of humans and let machines rule the earth? Actually, that wouldn't work either, these dynamics are inherent in any system with multiple independent actors and a drive toward making things better. If robots did manage to replace humans (ignoring the fact that this is already most peoples' worst nightmare), then the robots would simply find that all their institutions were impermanent and subject to collapse as well.
Seems like the easiest way to do this would be to use all the data from this breach to create a massive amount of noise in the credit system, making it virtually impossible for people working for these companies to do their jobs.
JoAnne Yates' "The Memo as a Management Genre" traces the origins of business writing, including the emergence of standard fields -- "From", "To", "Subject", "Date", and "In reply to", which actually predates the other four -- go Mutt and threaded discussion! The influences on subsequent communications formats, particularly Email and Usenet, aren't mentioned, but are obvious.

Letter-writing itself, as a widespread practice, is fairly new, it relying on post offices, stamps, and paper, and above all, literacy. The forms of letters written in the 19th century were very much defined by guidebooks and conventions.

Business writing itself is also highly formulaic, though it dropped much of the verbosity (and social grace) of earlier forms, discussed in this essay.

Messaging-as-technology, the protocols, conventions, forms, usage, and economics, are all mentioned, in particularly the induced demand created by easier communications, storage, and retrieval (or reversal as practices were limited or discontinued).

http://www.ismlab.usf.edu/dcom/Ch6_YatesMemoMgtCommQtly1989....
> For the first time, a meaningful number of developers are openly questioning the web platform.

Definitely not true. People were questioning the web app before there were a meaningful amount of web apps.
The entire credit system is a security nightmare. They all appear to use very basic "security" that has not been upgraded along with the rest of the world. Conflating identity and authorization, using deterministic values instead of random ones when necessary, and even for Equifax plain old sending people to the wrong domain.
That would mean that instead of the data being in a single centralized location it's on every single node. That's the opposite of what we need.

Edit: Assuming the colloquial use of the term "blockchain", a public database. In the sense that a blockchain is simply a data structure it's not necessarily a problem but also not a solution.
That is because America is not bound together by ethnicity or origin. We are not Americans because our ancestors have always lived in this place. What binds us together as Americans is the flag and patriotism. The flag and patriotism are supposed to transcend political boundaries. I for one think we as Americans need to emphasize what unites us and the flag and national anthem are two such things.
When you take out the great plains, the desert scrublands, and the alaskan wilderness, that 3.5% grows.
The web isn't the place to look for good tooling.

Properiatery low-code tools built over the web are a better starting point.
Is it "controversial" and "offensive" to some people? Then yes.

This is why I was so taken back when the left demanded censorship for "offensive" and "hateful" content. Don't the LGBT, atheists, etc understand that much of the country and even more of the world view them as hateful and offensive?

The greatest boon for the LGBT, atheist, etc movements was free speech. Free speech is want advanced their cause. Why attack it?
Microsoft Edge Charka Wrong Scopes in Deferred Parsing
Nope not legal but the FTC/others are really bad at enforcing it. Look at all the brand “embassadors” out there promoting products on personal accounts and trying to hide their affiliation as much as possible.
Because setting up a let's encrypt certificate is almost as easy as to making a self signed one. We're talking about typosquatting, having a completely valid domain of your own that is the same as someone else's but with a typo.

Edit: From what it is said in another comment, it's not exactly about typosquatting, but the author expresses the problem very badly. It seems credentials are sent to the domain before the certificate is checked. So one is vulnerable to DNS spoofing in e.g. a public wifi.
>If you've ever heard of the ORM/Relational impedance mismatch, it's got nothing on the set of impedance mismatches between the way servers like to work, the HTTP protocol (and its still very page-based orientation in a world of streams), the browser's DOM model, and how Javascript works, especially if you want to get excellent performance out of it.

Mapping objects to tables is a solved problem. The only noteworthy challenge is subtyping but it has easy solutions. I'm surprised how well it works even if you have an old crusty database with an archaic table structure. Compared to serialising objects to JSON or other formats that have no concept of identity it's downright trivial. However mapping objects to tables is the primary thing an ORM really does. Usually it implements lazyness for correctness so that your code while inefficient still works as intended.

What an ORM however does not do is write queries for you. Databases are remote devices, you can't just treat remote objects as if they were local (like CORBA did) if you care about performance.

Remember: You still have to write your queries but usually the ORM still helps you writing queries by providing a query builder or has it's own query language. The point of the ORM is that you don't have to manually marshall rows into objects, it's not a tool to avoid queries. It's right there in the name: Object Relational Mapping. It does not say AutomaticQueryGenerator or something related to queries.
I don't understand why they're proposed as a solution to this type of problem at all. I'm a big fan of blockchains, I work for a company/project completely reliant on them, but I don't get where people think they'll be useful for things like credit monitor and health care records. It makes no sense to me.
I had the opposite experience—the first time I read it, I barely made it through. The second time, before reading The Confusion, I re-read it, and fell in love with it. It gets better each time I read it.
That is not a senior developer, developer or even technology specific issue. You can experience immature egotistical indifference in any job. "Senior" developers who act like that are "senior" in title only.
Thanks, somehow I managed to grow up in the 80s without ever actually using Logo and getting LISP only in one programming course plus a little bit of Emacs (vi FTW!).
I've got springs now (Ikea), and a partner who moves often in their sleep. Having stayed in some Airbnb's recently with foam, the difference was huge. Planning on getting a Caspar or similar soon.
Text editors are much more complex than you think.
I have one right now, (I bought the mid level one) and I don't like it. Not comfortable on the long run and it seems it is actually smaller (by one inch in both sides and length) than my older mattress. If you are tall it can be a problem.

Good marketing, not so great of a product.
The first step of solving a problem is usually accepting there is a problem.
We have BitBucket at my job, I think because I showed my code during an interview through my BitBucket account it probably made me look good to my interviewer (now my boss) due to familiarity with tooling we already have. I can use any of them honestly. I use GitLab for private pet projects and BitBucket when I open source my projects, and then mirror to GitHub.
Hey, this is awesome! You literally built a product I specifically asked for here in a thread here recently: https://news.ycombinator.com/item?id=15002985 (it’s idea #2).

Great job! If you put a Massdrop-style portal here I think it could become an amazing way to find crowdsourced products and displace e.g. Google Shopping.

So here’s what you should do next:

1. Crawl every subreddit that can be mapped to a hobby and then crawl all product recommendations.

2. Use NLP and sentiment analysis to map recommendations to coherent products.

3. Rank products according to the sentiment across the subreddit and aggregate the feedback into a few key pros/cons.

4. Sort by ranking and return the products to the user.

If you nail this I would use it for everything. I constantly search reddit for product recommendations on places like /r/coffee. You can capture entire communities like /r/mechanicalkeyboards to appeal to those who trust real user reviews online instead of places like Amazon.

Here’s an example flow for this functionality: you arrive on the site and the interface prompts you to select interests. You do so and you’re then presented with products matched to that interest derived from crawling the relevant subreddit(s). You can see the most commonly expressed pros and cons for each product (for less functional products like watches: what users most commonly liked and most commonly disliked).

Based on my own personal experiences shopping like this I am convinced there is a startup here for the right execution. There are a huge number of people who use social media like reddit, Twitter, etc to do their shopping and this could become their shopping homepage.
I’m fascinated by this story. I was searching for a new mattress months ago. I found a casper.com case study from a web designer, which piqued my interest in a Casper mattress. After some research, I found sleepopolis.com. The site owner reviewed a dozen mattresses and his opinion was that Casper rated lower than its competitors, like Leesa, especially for side sleepers like me.

Later, the site owner mentioned he was in a legal battle with Casper and fully intended on going to war until the end. It was all over his site, blog posts and everything.

I was ready to buy a couple weeks ago so I checked sleepopolis.com again to check in and make a final decision. His site had been sold, all his posts about the legal stuff were gone and I remember feeling like the valuable “human-perspective” opinions of the writer were gone.

I would love to hear the perspective of the original Sleepopolis writer/owner - he built a valuable thing. Likely his deal prevents him from ever speaking about it publicly.

Side note: I bought a Leesa and it’s very firm compared to the W bed I bought a decade ago. It’s a few hundred dollars cheaper but we will probably return it before 100 days and buy W again.
silly author - sandboxed binary apps won't solve the problem. your whinges about client-server communication are inherent to, you know, clients and servers. whether the thing on the client side is real app or a web app is irrelevant. what matters is the communication. imagine if that channel could only carry keyboard/pointer input events to the server and static images in return. yep, that would be pretty robust.
For me the open web died when EME won. Someone should build an application platform from scratch instead of wasting more time on this crappy document platform with application capabilities.
It's really unusual for cities to shrink, let alone drastically, so rapping people on the knuckles for not planning what happens when half your population leaves is a bit disingenuous.
The problem is that if you present an average web user with the interface you can design (quickly and efficiently) in VB6, they'll spit in your face.

Much of the complexity of web design is not in the tools; it's in the fact that users don't expect a standard whatsoever, they just expect their UIs to be as slick and customly designed as magazines. If every website was written using the same standard, predefined set of widgets and components, the complexity would disappear.
That link explains the problem much better than TFA.
MS really had rapid GUI development absolutely nailed in the late 90s. For some reason we forgot all that.
But doesn't that render the term so broad as to be meaningless? If someone claiming to be a police officer wants to ask me some questions, and I ask to see some ID, and they provide it, by your terms that is a zero-knowledge proof, because they can't share the experiential knowledge of being a police officer.
FWIW, I see several examples with two numbers and up to four uppercase letters. There's a clear bias toward lowercase letters though.
Are you saying the famed American apple pie hasn't been a major contributor to America's success?!
Visicalc? How about a web app - Google sheets? It gains features every day and it's imminently accessible.

Numerous similar apps depending on what online platform you prefer.
JSON gets the most important thing right: it's simpler than XML. I probably should have rephrased my comment. I literally mean that it's a decent format, but not a great one.

One issue is that it's surprisingly poorly specified: http://seriot.ch/parsing_json.php.

As a data-interchange format, it lacks first class dates/timestamps, the issues about specification are a pain when dealing with numbers (depending on language, you may not be able to use the full range of 64 bit ints), and has no builtin concept of schemas. That said, I'm not sure what I'd recommend above JSON, though you clearly wouldn't use it for really high performance servers.

It's also used as a configuration language, where more issues surface. It doesn't accept trailing commas or comments (I can see the argument for requiring all keys to be quoted, but that's a pain to write as well). For configuration, I think I prefer TOML to JSON. Dhall looks cool, but I've never used it.
> Depressed people and diabetics are hurting themselves either through action or inaction, but I've never been threatened by a diabetic or depressive outside a Circle K.

Well, make the treatment for diabetes unavailable through legal means and very very expensive - and you soon will be.
Curious: Did you consider the Purple? I tend to get pretty hot at night (no AC) and that one seems to boast the best marketing jargon with regards to cooling. Can you speak to the breathability of the others you've tried?
Even the wealthy should worry about such a world, since you never know when you might end up in the ER with no papers.