skysight-inc/HackerNews huggingface dataset:
> Both don't say much without good changelog.

This is a good point. Good changelogs, like any documentation, take a lot of effort and so are unfortunately quite rare.

As an API consumer, to me the ideal upgrade-related documentation includes:

* Detailed release notes for each released version

* For non-GA releases like alpha/beta/RC's, describe the changes since the last small release -- typically consumers of a beta are following dev quite closely

* For GA releases, pretend the alpha/beta/etc don't exist at all. Describe the delta from the last GA release. Consumers don't care about the fix for a bug in a beta they never even knew existed.

* When you do breaking changes, provide upgrade guidance, like "If you were doing x before, now you should do y + z instead"

* If appropriate, consider also keeping separate upgrade guidance documentation for major breaking changes, for those laggard consumers that are going from a much older version like 2.x to 4.x. This allows someone to follow more of a checklist to get up-to-date without having to read 900 pages of individual release notes

You can do this with date-based version, but it's much harder as a consumer to figure out unless there's very good documentation. If I'm upgrading from "2.0.4" to "4.1.1", I know as a absolute minimum starting point I will be looking at release notes for "3.0" and "4.0" and from that, I should get a pretty good sense of the overall effort involved. If I'm upgrading from "2016-11-05" to "2019-12-19", how do I do the equivalent evaluation?
Redis themselves offer a managed service. There's https://www.envkey.com/ and several alternatives. Elasticsearch offers 3 completely different tiers of support and offerings.

Everyone going to AWS is going there for an AWS-like experience. As someone who runs pretty big workloads on AWS, you still very much need the help when you get to a certain scale, and there is a ton of value in just buying a support contract from Elastic or Redislabs, even when using their managed services or running it on an ec2.
To be more accurate, the speed with which electrons move through the wire is rather low (which does not matter, of course, because the signals are carried by the electromagnetic forces which propagate very quickly).
There are lots of apples to oranges here. You can't compare say a Linode or Digital Ocean to an AWS/Azure. One of boxes for experimentation may make sense, I would not run prod though. Also, have you seen the network performance of the smaller providers? (obviously that comes at a cheaper cost too)
I upvoted it because I wrote and spoke this last 20 years.

Keyboard buffer. You know what is keyboard buffer?
I suspect one answer may be for the Smart Fortwo and the other for the more recent Mercedes sedans. The Smart cars likely don't have much residual value.
Robot sex will be the next big thing.
Show HN: Easily track news and releases for JavaScript, Python, Ruby, Elixir
If you keep your computer in suspend-to-RAM mode, it will do that and still use less power over time than the C=64 and its damn power brick.
I think you misunderstand where I’m coming from with my line of questioning.

I’m asking questions because we provide tools that standardize the API development experience. Semver is trustable if the tools create the contract instead of the developer that decides to build the API. We deliver the tools that create the contract.

In this sense, APIs built and delivered atop our platform don’t need to “encourage best practice,” best practice is — or at least can be — hardcoded in with no potential for footguns.

Your concerns about semver are well-founded. I’m asking questions because I’m pondering aloud if we can fix them and change semver — with respect to APIs — from a social contract to a coded contract, and include tools necessary to inform end-users of API changes. :)

Does that make more sense?
If someone dismissively thought "we're smarter now", would they bother to study history?
Right. In this case he plead guilty and admitted to having done it. I am just curious as to which specific laws he broke and whether it is possible to inadvertently break these laws by being a horrible programmer.

If he had intentionally created a spaghetti code mess that just happened to break from time to time would that be different? I assume intention is difficult to prove in court but I am not an attorney.
See also:

https://en.wikipedia.org/wiki/Wirth's_law
It's almost certainly not 4chan imo. It's a real dev, with a name, profile pic, website, contact info and repos.
To check at what point the system is responsive enough to launch a browser. So, not just calculating the boot times (we have that already), but from power on to launching a browser.
I'm pleasantly surprised! They took the route of "promising but underdeveloped technology" rather than settling for a well-developed solution that compromises their principles (which, frankly, I wouldn't have faulted them for; at the end of the day you still have to get work done). With luck maybe we'll see Mozilla contribute to Matrix? There is, after all, an implementation written in Rust: https://github.com/ruma
The predecessor for systemd on Fedora was upstart, not van Smoorenburg init.
Huh. I guess it’s not too surprising, but that doesn’t work at all. init gets special treatment for signals.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
And here you have walked straight into the trap. If you are an uneducated white male who has been unemployed since the steel factory went under, the economic ascendancy of women and minorities is not a measure of the country's greatness, it is a symptom of its moral decay. Our infrastructure is crumbling. Our military is impotent. Our factories are shuttered. Why? Because of affirmative action, which propels people into positions they are not competent to hold simply because they lack a Y chromosome or have dark skin. It's such an obviously stupid policy. It amplifies incompetence, and today we are paying the price.

(Please note: this is not my point of view. I'm channeling the Right simply to demonstrate how their rhetorical techniques work.)
I agree I think this is generally more accurate. Browsing the web, writing documents, and navigating around (modest sized, not enterprise size)spreadsheets feels much slower than it did in the late 90s/early 2000s. I won't go back as far as 1983, but maybe 2003?
Why Dating Is Hard for MIllanials?
I read the whole thing. I thought it was a pretty trash rant. My thoughts while reading roughly went::

"Everything was blindingly fast in the 80s!"

- Yes you fuckwad, it was the 80s and the vast majority of content was local to your machine, or your machine was really just a terminal wired to a nearby mainframe. Do I need to link the "latencies every programmer should know?" article yet again?

https://people.eecs.berkeley.edu/~rcs/research/interactive_l...

The delay is not some UI designer out to get you, it's a fact of life when the data you want lives on a machine that is remote. Sadly RTT is still bound by the speed of light.

That's why there's a freaking spinner. Your computer and the UI has SO much time to kill waiting for the network that they can render a happy little dancing spinner for you.

"The mouse is a terrible invention"

- Oh really? I think it's actually a great tool for pointing and clicking on things. I grew up playing video games on computers. The mouse is first class input device that works incredibly well.

Better yet, its use doesn't vary all that much based on specific context and application. Yes, you had memorized your POS system well enough you can do it blind! Great, now fuck off. I use my computer across hundreds of applications every day. I have no desire to become a master of the hotkeys of each of those applications. I'd like to reserve the space in my head for things that matter.

"I want to clarify that I am literally talking about the future of the human race and I am deadly serious about this. It's not about me."

- No, I actually rather think it is exactly "about you". The author has failed to acknowledge the INCREDIBLY VAST expansion of a computer users reach over the last 30 years. I vividly remember playing my first multiple computer game. I was 10 and the computers had to be wired together with an old DB9 COM cable (branded a "gaming cable" at the time).

Now I can literally watch webcams on the other side of the world from my house. I can click a few buttons (on my shiny mouse, I might add) and start a chain of events that leads to direct action on the other side of the world, from shipping me cheap shit or to planting trees.

I can work from my house and still do my job just as well as if I were in the office. I can have a coworkers who live in Ukraine, Spain, Netherlands, Germany, etc. Not only can we be productive, we can laugh and chat online, or using video calls.

BUT FUCK! How dare they add some latency in the process of getting you all that.
Gas station or McDonald's on the route to some far destination. I've done this in the android app and it works but it can be a little awkward.
Apart from the Aerion as2 i dont think there are many other credible supersonic aircraft in development other than the Nasa one. Concorde, other than the booms, had engines so loud, and i mean insanely loud they would not be popular these days. I remember covering my ears as it flew overhead.

I do find Elon Musks frequent mentions of a vtol ss aircraft quite interesting.
Electric engines would not have the same issues at high altitude as conventional ones. Battery density is starting to get in the right area to make this feasible.

He is frequently distainful of flying cars but one logical conclusion of this is indeed potentially flying cars (Tesla secret projects anyone?). When you think about how much of the world is inaccessible, one of these would make a great thunderbirds style exploration vehicle ( provided it had a large expandible solar array stowed somehow) . Fancy a trip to the Kamchatka ground zero? No problem! I wonder whether aerodynamically they would not need to be so concorde like and maybe just bullet shaped. Perhaps on Mars you could have supersonic blimps
Search for destinations along your route is (finally) a feature in the gmaps mobile app. It isn't in the web-app. Apparently Google agrees that it is a desirable feature. Why does the UI-limited, small screen experience surpass the rich desktop experience?
Some years ago I worked on a very popular Windows desktop C++ program that had to stay small and backwards compatible, which meant only Win32 APIs and homemade libraries. Designers by the dozens would be hired, then get fed up with these limitations and quit, complaining that they wanted to have the freedom to make UIs in HTML and CSS, and that users are used to interacting with Web UIs so everything should look like that.

Later, at a different job, the UI was Electron based, but designers no longer worked in HTML, they used some other tools and it had become the job of engineers to write the HTML and CSS to match.

These trends seem to be driven partly by conventional wisdom about the lowest common denominator among young people in the workforce, e.g. javascript and html are so much easier, let's build everything on those, and next thing you know those have become a given and the next crop of kids will use something new on top of that. Or maybe something like QT will win and native code will become a first class citizen again with secondary support inside browsers via WebAssembly?
Generally, denying people access to healthcare in for the sake of experimentation is unethical.
I agree with much of this mainly because as a teenager in the ‘80s, I witnessed the speed and efficiency of secretaries navigating Wordperfect’s non-GUI. The POS ui in the tweet thread is similar. There’s certainly room to rethink the use of GUIs everywhere for everyone.
Agreed. Velocity of input is not nothing, but I think the original premise set up in the first tweet of the thread—that modern computer software makes us wait too much—is lost by focusing on an input mechanism, which would suggest the root problem is the human's ability to provide input.

I contend my chief complaint with software, in any context, is that it makes me wait while it responds to my input, regardless of how I provided that input.

Modern software:

* Often cannot keep up with typing.

* Often cannot keep up with mouse actions to, e.g., show highlights on hover or indicate interactive elements because there are too many third-party scripts executing (or whatever).

* Takes too long to display results, again because of being too busy executing software components (trackers, ads, bloated client-side frameworks, whatever) that is not expressly related to my action. Also because server software tends to be written using inefficient languages, platforms, and frameworks that theoretically optimize for developer efficiency (arguable) at the expense of user experience. Every time I interact with a web site that is slow to respond to network requests, I am usually right to guess the server is PHP, Ruby, or similar.

* Infantilizes the user by providing a too-narrow set of actions (the curse of "mobile first"), narrowing the functionality and in many cases causing things that should be relatively easy to require lots of steps. This may be where he was going with the remainder of his thread, but I think it went off the rails, as you said.
Great point. Or motors in the rear wheels could probably get it up to 100MPH on the runway before the jets had to take over.
Traders Got Advance Feed of Bank of England News Conferences
You can search along the route if you are navigating, however I agree it could be improved in that you don't get to see any details of a place or add it to saved places (you either add a stop or don't). I don't think Maps is bad for this reason but I agree it is possible to improve.
True.

Semver is like unsound type systems or TDD, most of the time it's okay, until it isn't.
Algorand's Core Protocol
> I don't think I said all that

Kind of: "inexperience", "lack of research", "don't want to learn C++"

> Making a GUI isn't really that difficult.

Also a big assumption, especially for cross-platform GUIs.
I've heard the "eye of Sauron" metaphor in a few podcasts that commentate on the ease of mass surveillance. This has less to do with individual smartphone tracking - individual smartphone users have the power to zero in on certain topics and ideas (viral) relatively instantly since news can travel along a global internet unhindered.

Chinese Social Credit automated aggregation of all citizen smartphone activity feeds is the "rule of Law". We will be economically limited by our inefficient (bad) deeds.
I wish they changed the spec so iterating over a null Iterable would not throw an NPE:

Iterable items = null;

for(Object x: items)

{

// will not enter the loop

}
Easier said than done. To implement that I will probably need to hire a DevOps guy, and now we have all this cloud formation (or whatever your infra as code choice is) code to manage now. So in reality it probably costs more (devops and more code to manage) than if I just went with a couple cheaper bare metal servers.

If you are running in the cloud then you still need a devops guy same as you would if you where bare metal. In fact you will probably need _more_ devops people the deeper you get into the AWS ecosystem.
I think you might be confusing semantic HTML with the semantic web. (Which is understandable given the mention of semantic tags.)

Using semantic HTML means using <article> rather than yet another <div>. What GP is referring to, however, is adding extra information to your HTML detailing what kind of data is in your tags, e.g.:

<p vocab="http://schema.org/" typeof="Person">
<span property="name">Christopher Froome</span> was sponsored by
<span property="sponsor" typeof="http://schema.org/Organization">
<a property="url" href="http://www.skysports.com/">Sky</a></span> in the Tour de France.
</p>

Here, the vocab, typeof and property attributes are used to add semantic information to the HTML. It might also give you an idea of why one might consider that a chore, especially if it doesn't appear to provide any benefit, like making your site accessible to users of screen readers.
Maybe you can check the feminist movement history. For example, many were against abortion for various reasons, one of them was that it allowed men to pressure them to get one.

You can read prostitution legalization as a right to choose to use your own body for profit or you can read prostitution banning as the right for not being used for profit from your body.

Many imagine is a simple thing but all the other values come into play.

Some people think a embryon is more important that a women choice. Some think that right to sell your body is more important than to legally allow women oppression through sex work.
EU Legal Opinion on Facebook Case Spells Trouble for Data Transfers
Europe’s Largest Medieval Square
I have seen multiple feminists make the argument that the phrase "selling their bodies" also applies to football players, chemical workers[1], coal miners. I find it fairly persuasive.

[1] https://www.youtube.com/watch?v=edAxujKev1I
I feel like a large part of the unintuitiveness of keyboard interfaces is not actually an intrinsic quality of keyboard interfaces since they're so often conflated with command-line or TUI interfaces. There might be an alternative but yet undiscovered paradigm which combines the best of both worlds: keyboard control and intuitive, beautiful, graphical widgets.

To motivate this with a somewhat blunt example, what if we had a typical GUI but named each control (button, field, etc) with a short code (1-2 letters), in the style of Vimperator/Tridactyl/Vimium? You lose none of the intuitiveness and discoverability, but suddenly you can select the control much more quickly and precisely than clumsily trying to point a mouse pointer onto it.

And that's just a silly example I came off the top of my head now. There may be much better keyboard-centric yet intuitive paradigms.
It is true that AWS is expensive considering cost of raw hardware resources. However, it is also true that it is very easy to create many kinds of apps and their support is not bad. For example using their "serverless" stuff (lambda, api gateway, static hosting in S3 and cloudfront) it is very easy to make apps with hosting cost almost perfectly matching the number of users so the only upfront capital expenditure is dev time. Another thing that is very easy on AWS is micro service apps (geographically distributed or not) consuming their managed services such as elasticache etc. Finally, automated deployments (allowing for continuous development/continuous integration if one wishes to use it) are also easy to implement quickly...

The price one pays for it is vendor lock in. I wrote many mini-non-mission-critical apps to run on AWS, but I would think twice about putting my main business app in AWS without (costly)backup.

I imagine that for startups it might make sense to create their initial product on AWS and when the product takes off spend some of first revenue making it cloud agnostic.

The benefit of AWS is that a startup can implement a proof of concept quickly without having to worry about managing their own elastic search for example, and once it proves viable effort can be added to escape vendor-lock-in.
The standard mouse hardware allows you to move the digital pointer relative to it's current position. That means you know need to know where the digital pointer is, and that's 100% visual. You could set up audio cues too give location feedback, but that's still not a great solution.

If you use the same digital pointer with a drawing tablet that maps its surface to the screen, then you can set its absolute position on the screen. You now have physical feedback about your pointer's position, as well as visual
It's not anthropocentric to ignore the least likely possibility until presented with evidence to the contrary.
Nothing you said is a rebuttal to my previous comment. Please argue with sources or it's just your opinion, and it's irrelevant as it doesn't answer the question of whether "legalizing" sex work decreases sex trafficking. It clearly does not according to my sources.
The Feds Get Permission to Seize Edward Snowden's Book Profits
Should there be? This seems more like a civil matter.
> I fear for the day when the influencers and streamers make their way out of their bedrooms and into our public spaces, and we'll all be part of the show.

I read a lot of complaints about Instagram influencers at Burning Man and how people (men) are trying to sabotage their video shoots by wandering behind the shot with no pants on.
Google has an alternate interface to maps called "My Maps"[1] with the kind of editing and composition features the author misses. I use it all the time to make maps for road trips with lots of points of interest and complicated routes.

[1] https://www.google.com/maps/d/u/0/
Thank G-d. I have been saying this for year. Code is:

- Getting less stable
- Getting less speedy
- Getting less efficient

I blame the fact that old programmers and young programmers do not have the appropriate relationship.
I enjoy reading reddit, hacker news, etc, but I wanted to look at one page and get a quick sense of what was happening with the tools I use. Is there a new version out? Is there an important announcement from a package maintainer?

I built Version Conflict (https://www.versionconflict.com) to scratch that itch. It's built in Elixir/Phoenix and has less than 100 lines of javascript.

Wanted to share it with people who might find it useful and solicit feedback / feature requests. You can click around to browse by topic or you can register to create custom feeds to see everything in one place. Any feedback is welcome. Thanks!
Recently car2go added a $1/ride fee that was for insurance. If you reached 99 trips in a year, you didn't have to pay that fee (or similar).
> in 1998 if you were planning a trip you might have gotten out a paper road map and put marks on it for interesting locations along the way

In 1998, I used https://www.mapquest.com/ to plan a road trip a thousand miles from where I was living, and it was, at the time, an amazing experience, because I didn't need to find, order and have shipped to me a set of paper road maps.

In the 1970s, when I had a conversation with someone on the phone, the quality stayed the same throughout. We never 'lost signal'. It was an excellent technology that had existed for decades, and, in one particular way, was better than modern phones. But guess what? Both parties were tied to physical connections.

Google Maps is one product, and provides, for the time being, an excellent experience for the most common use cases.

> amber-screen library computer in 1998: type in two words and hit F3. search results appear instantly

So that's a nice, relatively static and local database lookup, cool.

I wrote 'green screen' apps in Cobol for a group of medical centers in the early and mid 90s. A lot of the immediate user interface was relatively quick, but most of the backend database lookups were extremely slow, simply because the amount of data was large, a lot of people were using it in parallel, and the data was constantly changing. Also: that user interface required quite a bit of training, including multi-modal function key overlays.

This article has a couple of narrow, good points, but is generally going in the wrong direction, either deliberately or because of ignorance.
Can't wait for Mozilla to back a stable, native desktop client into a daily driver state so we can finally ditch Mattermost at work.
Edward Snowden just gave me permission to steal and distribute this book. Have fun
I am still a fan of Googles OpenRefine tool. It's reconciliation feature that helps disambiguate Named Entities etc based on wikidata is really powerful - https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation

You can hook in your own reconciliation end point which we do at work to expand internal knowledge graphs.