skysight-inc/HackerNews huggingface dataset:
First of all, please stop making sweeping generalizations, "people prefer", "almost everyone", etc... Without proper citations, these claims are meaningless.

Second, more concise doesn't always mean better, let alone more readable or more maintainable. It's often the opposite.

Third, functional programming is usually preferred because of aspects such as composition or immutability, not conciseness.

Fourth, rewrites of an existing code base usually leads to shorter code bases, simply because of the acquired knowledge, regardless of the language or the techniques.
For rendering rates measured in frames per second, maybe check out "Real-time Rendering", currently on its 4th edition. https://www.realtimerendering.com/

For rendering rates measured in seconds per frame, consider the "Physically Based Rendering Textbook", currently on its 3rd edition. https://www.pbrt.org/
Wondering why this bit isn’t open source. Is there really any point? There exists open source VS Code extensions and forks that do basically the same thing. It’s weird for the whole editor to be open source but for this part, admittedly very compelling, to not be. Something is fishy.
Huh? I’m using a German keyboard with en-US Windows without problems.
I had exactly a children's book like that in the 80s, in a communist country.
> get performance near the ballpark of C++ and family.

That's a bit of an overstatement, Swift isn't really in the same ballpark than C++. Its performance characteristics are more the like of a managed language.

In the ixi driver implementation[1], they ended-up with results comparable to JavaScript in terms of throughput[2], and C# in terms of latency [3].

[1]: https://github.com/ixy-languages/ixy-languages/blob/master/R...

[2]: https://github.com/ixy-languages/ixy-languages/raw/master/im...

[3]: https://github.com/ixy-languages/ixy-languages/raw/master/im...
You should understand the argument before you form an opinion on it. First of all, there are plenty of us who have legitimate use cases for web push. Second, if you care about being bothered by shitty sites prompting you unprovoked, you have a couple options: content blockers or use different sites.

The need for notifications is real and Apple’s choice to exclude their availability in iOS is a business move not a technical move or a users-first move. Making PWAs better on iOS runs counter to Apple’s walled garden business model.
I have a Jetbrains Toolbox subscription.
For an overview: Real-Time Rendering 4th edition by Haines et al.

For advanced techniques:

- GPU Pro and GPU Zen series (ed. Engel)

- Ray Tracing Gems (Haines et al.)

- Unreal Engine tutorials and source code for reference implentation
The problem is, Does the majority of the developers contributing to Linux believe in this code? Or is it forced upon them by political activist that doesn’t do much coding because they spend much of their time on ‘social justice‘?
Trac was/is truly to most awful bug tracking system. I mean a primary function of a bug tracking system should surely be to accept bug reports from users, yet Trac manages to make that the least discoverable and least usable feature. Even things like subscribing to an existing bug report or listing bugs are very hard to find. I would say "impossible" for ordinary people, but will get accused of exaggerating, but go and look at a Trac-based bug tracking system some time to see what I mean. One at random: https://trac.osgeo.org/geos
Making the web suck more to match the native experience would be stupid. If people wanted the inconvenience of native apps, they'd use native apps.
What a glorious world that would be... I'd absolutely upload you a car, if you upload me a good drink. Or maybe we can put a FOSS car on GitHub?
SEO Job Description
React Native Travel Article App UI Clone #6: Finishing Up List Screen
It says that, but it’s wrong. California has no statute of limitations on murder. This was recently demonstrated in dramatic fashion when the golden state killer was arrested for murders committed 30 years prior.
You simply have a single uncaught-exception handler and that takes care of the problem that you mention.

Instead of 500,000 if err != nil checks littering the source code and making functions unreadable.
It's very avoidable, it only asks on first boot of a new user account.
This reads like a reddit post, but with a hakcer news twist. As always,in these kind of situations, I would suggest looking deep inside your heart for an answer, and not the forums.
He wasn’t wrong on the second, it is very evident that it is.
Accepting bug reports from users isn't necessarily a goal of bug trackers: in some workflows mailing lists are better for unconfirmed bugs, the actual bug tracker is for confirmed bugs (read: not submitted by users). It works better that way a large amount of the time.
I was day dreaming today of doing the opposite: attaching a modern mechanical keyboard to some sort of printing device. I figure an electric typewriter like this would be ideal for this kind of project. A dot matrix printer might be more hackable...
> Remember when browsers had an address bar and a search bar?

Well, my pet theory is that this is the same as Facebook's internet.org program: just how Facebook wants to (and benefits) to train the "global" (sub)conscious that Facebook essentially is the Internet, Google stands to profit from everyone confusing/conflating Google search results with the Internet.

Why give people an address bar when they can (slightly) misspell their destination and go through Google instead? Maybe, if they're lucky, over time, every network request will go through Google.

I've also noticed this in how Google mandates the placement of the Google search widget on the home screen on Android devices. Place "the Internet" front-and-center on everyone's favourite screen, and people naturally "fall in."
Postgres provides LISTEN/NOTIFY for precisely this sort of use case.

https://www.postgresql.org/docs/9.1/sql-notify.html
You're trying to draw a comparison between app developers supporting multiple CPU architectures for their applications, and web developers continuing to use JPEG and PNG files for their web sites. I honestly just don't see how this comparison works.
You certainly want a good way to sort, classify, combine and remove reported bugs (which Trac also makes awful), but you should never put up barriers to accepting bug reports. My rule of thumb is that every bug that someone reports affects 9 other users who couldn't/didn't report it. (Probably with Trac it's 1:99 because of how difficult it is to use.)
They make efforts to cast the coders as young people who can be swayed by marketing gimmicks instead of real workplace concerns like benefits, livability, consistent work/life balance. That culture permiates the entire engineering culture
No mention of PWA features (specifically manifest/installation/web push) is so lame. Classic Apple politics.
> "It accuses Amazon of “tying” its marketplace and logistics services together, an antitrust violation in which a company uses dominance in one market to give itself an advantage in another market where it’s less established."

Amazon has robust competitors in the shopping space (hello Walmart). And does not often serve niche markets. Hobby electronics (think old radio shack or current adafruit), sewing, wood screws in volume are all places where amazon falls flat and there is plenty of room for others to succeed.

What amazon is doing is brilliant, it isn't monopolistic, it is vertical integration. Something that doesn't happen as much as it once did.
I agree that most companies won't ever need to shard, and pre-sharding (or worrying about extreme scalability challenges in general) is usually unwise premature optimization. But it does depend on the product category.

Social networking and user-generated content products (including GitHub) need to be built with scale somewhat in mind: if the product reaches hockey-stick growth, a lot of scalability work will need to be completed very quickly or the viral opportunity is lost and the company will fail. I'm not saying they should pre-shard, but it does make sense to skip FKs with future sharding in mind.

This was nearly a decade ago, but in one case I helped shard my employer's DBs (and roll out the related application-level changes) with literally only a few hours to spare before the main unsharded DB's drives filled up. If we also had to deal with removing FKs at the same time, we definitely wouldn't have made it in time and the product literally would have gone read-only for days or weeks, probably killing the company. Granted, these situations are incredibly rare, but they really do happen!
Okay, you've named one web site that will stop working for it at the end of the year, because of a choice you're explicitly making.
One of my first software roles was working with a legacy FileMaker database where most of the business logic was built directly into different GUI elements. I do not envy your work.
An African Child’s Dream Comes True – Sho Madjozi
Next one due in 2021
> No compiler can know that a string variable is a "name" or a "password".

In pretty much any language supporting user-defined types and/or type aliases, types can be used for that information (with aliases, providing documentation the same as hungarian notation does; with real types, providing the possibility for enforced protection against accidental misuse.)

But the article doesn't actually use hungarian notation for that kind of thing, it uses it for traits that are not "what it does", but instead metadata analogous to Ruby's "taint". Which, again, is something easily encoded in typing, in a static language, either as a core feature of typing or via user-defined (possibly wrapper, depending on other features of the type system or general language semantics) types; type aliases, even, would work as well as hungarian notation, but using actual types lets you put guarantees in place rather than just providing documentation.
> The need for notifications is real

Do you keep metrics on acceptance rates? How many of the notification prompts that you pop up are actually accepted? How much of the time are you just annoying your users?
There are countries in Europe that have already made this better world. It is possible.
If you tell people to submit bugs to a mailing list, that means that devs will manually confirm bugs before putting them onto the bug tracker: this gives an incentive to get them taken care of faster, because right as it's added, someone who knows the codebase has a general idea of what's wrong.

Mail is standard, so it's not really a barrier. It kind of lessens the Caps-Lock Warriors of Bugzilla-like systems, though.
All of macOS's system libraries are dynamically linked, so there's just no way Swift could be used in the OS if it didn't do this right.
I love Rust but comes from an Ocaml/F# background (and, as others have said, the inspiration is palpable) and you seem to have a common misunderstanding around immutable datastructures.

Immutable datastructures in functional languages are not datastructures that cannot be mutated, they are datastructure that efficiently produces a new, updated, version on each operation (such as the cons list).
While they are slower than traditional datastructure for a typical use case, they tend to be a lot easier to think about, make parallel code much easier and let you easily get back in time to previous versions of your datastructures (when discovering rust, I was actually disapointed that they were not available in the std).

The im[0] crate offers what seem to be good Rust implementations of that kind of datastructures (with abetter explanaition of why you would want them).

[0]: https://docs.rs/im/13.0.0/im/
Why do we need ABI stability for these features?

Libraries can evolve just fine by providing backward compatible changes as far as I can tell?
Who is the real Dice Man? The elusive writer behind a cult novel
Less 200 people die canoeing in the US every year [0], so I don't think it is particularly dangerous. Surprised your canoe sank though, usually they are supposed to have air pockets so they float even if full of water.

[0] https://www.adventuresportsnetwork.com/sport/paddle-sports/w...
Is this a paid ad? Don’t get me wrong, I have the late 2016 MBP with the TouchBar but “ disastrous“ is pretty harsh. The hardware besides the keyboard has been fine.
PWA is not one single thing that needs a special mention, bunch of features they have listed will account for a better cross platform web & mobile experience.
Ooh, Meeting Owl. We used one in our company get together last week and they are great (also incredibly expensive, about £800 in the UK). But yes can second this one.
Like I said, our use case is legitimate in the strictest sense. Users request to enable notifications themselves. We never automatically prompt for it. So like.. 100%.
Most medium sized, and above, dogs could bite your hand off no problem.

Ya’d need to keep them in an enclosure. They breed in captivity fine.[1]

I wonder if they could be bred to become house pets. Could take a while.

1. http://theconversation.com/tasmanian-devils-reared-in-captiv...
Liked how the team decided to play devil's advocate to their existing way of working. More often than not, one tends to lose focus on why they are doing it and if it makes sense.
Equally important is creating a sense of security where everyone voices opinions without fear of judgement.
Pleasantly surprised that despite working remotely, the team managed to split responsibilities for retreat amongst them instead of making it a one-person show!
> Some of items cannot even be googled, what's "Turbo DFG"?

Data Flow Graph, JavaScriptCore's optimizing JIT.

https://webkit.org/blog/3362/introducing-the-webkit-ftl-jit/
The first time this happened, to a friend of mine whose parents out a photo for her, I found it really creepy. I still don't like to visit her grave. It makes me curious how differently people process grief.
Itanium failed, in part because it broke compatibility. AMD succeeded with x86_64 precisely because they realized that supporting the programs people actually used was vital.
> There are plenty of us who have legitimate use cases for web push

Such as? The only use case for notifications and PWAs I'm coming across are clickbait news sites creating a sense of urgency with "homepage was updated" modals obscuring content and capturing click events. Web user agents have freedoms in rendering pages to users, and Safari siding with users and power efficiency is a good thing. In line with other comments, I predict browsers will soon provide opt-out for notifications, then eventually deprecate them altogether, like they did with popups/popunders.

Now, more importantly, Safari could work on their odd pick list control rendering like a dial wheel.
Linux Smartphone PinePhone Will Be Available to Pre-Order Next Week
If 25-50% of your users used RasberryPis to run you app you’d support it properly.
wait is that "the argument" we're supposed to understand? you know, just because I use alert() in my code to debug doesn't mean that it should necessarily actually... work, and stuff... tl;dr - the tragedy of the commons exists; hence, lots of shitty technology that would otherwise be prone to it doesn't exist.
Can I take this opportunity to ask a stupid question?

Is ML anything more than pattern recognition? If I could tally nearly every game state vs game state -> win %, then run a simple if [state], then {} program, then what do I miss out on vs an ML approach? Is the magic just in how we feed good data sets to an ML algorithm so it can efficiently mimic the above much quicker?
Off topic: can already assembled 6502 kits (i.e. single board computers) be bought anywhere, just like this one for z80 https://shop.mcjohn.it/en/diy-kit/22-33-kit-z80-mbc2.html#/1... ?
None of which particularly contribute to being able to supplant an iOS app with a PWA. Which is intentional on Apple’s part.
How is this different than every other company doing business in China, including Microsoft?

>Keep your data within datacenters located in China with an Azure China account and stay compliant with international and industry-specific compliance standards. Access to your customer data is controlled by an independent company in China, 21Vianet. Not even Microsoft can access your data without approval and oversight by 21Vianet.

https://azure.microsoft.com/en-us/global-infrastructure/chin...
In the linked blog post they mention size explicitly:

> ABI stability for Apple OSes means that apps deploying to upcoming releases of those OSes will no longer need to embed the Swift standard library and “overlay” libraries within the app bundle, shrinking their download size; the Swift runtime and standard library will be shipped with the OS, like the Objective-C runtime.

For new UI backends you don't need a different interface, you provide the new UI under the old interface. If your new elements have new behavior you will need to update your app anyway.
Then they have to subscribe to the mailing list, which is another set of extra steps. Some people only know the web exists and don't even know mailing lists are a thing.
Russia Is Building One of the World's Largest Facial Recognition Networks
Able to answer this since I just read an article on this in the Economist (https://www.economist.com/science-and-technology/2019/06/29/...): It seems whale genes have evolved to supress cancer. These include ATR (https://en.wikipedia.org/wiki/Ataxia_telangiectasia_and_Rad3...) that senses DNA damade, AMER1 (https://ghr.nlm.nih.gov/gene/AMER1), which stifles cell growth, and RECK (https://en.wikipedia.org/wiki/RECK), which suppresses metastatis.

These genes are also found in humans but the hope is that studying genes from animals like elephants and whales we can find ones that we don't have.
> Such as?

Such as a user presses a button in order to enable push notifications.
Not if you actually solve the problem.. which is basically just to make the permission only possible if the user interacts with the page in some way that satisfies a heuristic.
Europe basically shipped its rejects to the US (and Australia), then likes to claim moral superiority and better ability to play "let's all just get along."
Not directly in answer to your comments, but if you work for a remote company then meeting up 2 or 3 times a year for a week is part of the trade-off. The rest of the year you're at home for the partner/kids/pets.
Yes, but the guarantees Swift provides are not a requirement for that.
If only a compiler/runtime was somehow endowed with enough artificial intelligence to decide on optimal data structures and algorithms to provide this magical 'fast by default, optimal by fine tuning'.

High level languages are fat, inefficient, rigid and what every large corporation wants, because they share so much in common.
url: projectpage.tld/bugs

Hi! If you're here, you must have found a bug. Send an email to XXX@projectpage.tld describing the bug, and we'll see to fixing it as fast as we can, and we'll alert you when we've started working on it!

You don't have to have them subscribe, necessarily.
One of JavaScriptCore's optimizing JITs.
WebKit uses Bugzilla: https://bugs.webkit.org
Adding support for a CPU architecture is often a considerable amount of work, and the pay-off is often small, although this of course depends on what kind of software you have. For typical applications for end-users the cost/benefit ratio for supporting anything other than x86 is typically very low. For other types of applications like servers it's higher, so they often do support arm, s390, ppc, etc.

Supporting jpeg however is very low cost, with very high benefit: about 20% of browsers don't support webp. It's a small nuisance, not a substantial amount of continued investment of work like supporting a new architecture.
I answered to that in the last paragraph. I don't see the appeal in 2019, in particular in the Apple ecosystem where backwards compatibility is not respected that much.
Didn't early humans also rarely get cancer?

My understanding is that cancer is one of those things you die from if you don't die at child birth, get eaten by predators, or get the flu, polio, malaria, the plague, etc.

That is, the reason cancer is such a big deal in modern times is because other causes of death have been controlled.

I don't know much about elephants but I imagine cancer is still low on their list of things to worry about (humans are probably a lot higher up) If they started living a lot longer, it would probably show up more.

People under 40-50 also rarely get cancer. Although I'm sure the human environment has produced some more causes of it that make those rates higher than they used to be.
To me, the message queue is simply a substitute for polling the DB, not a way of persisting message status. That is a job for the DB.
"One thinks of the big wooden box, locked, in Isaac Newton’s rooms in Trinity College. In this box he kept alchemistic manuscripts, deistic tracts and other occult materials."

Interesting thing is, most of the contents of this box was later bought by Keynes, he has a great lecture on Newton being the last magician, i.e. pre-Newtonian: http://www-groups.dcs.st-and.ac.uk/history/Extras/Keynes_New...

What became of the box?

"They remained in the box to shock profoundly any eighteenth- or nineteenth-century prying eyes. They became the possession of Catharine Barton and then of her daughter, the Countess of Portsmouth. So Newton's chest, with many hundreds of thousands of words of his unpublished writings, came to contain the 'Portsmouth Papers'.

In 1888 the mathematical portion was given to the University Library at Cambridge. They have been indexed, but they have never been edited. The rest, a very large collection, were dispersed in the auction room in 1936 by Catharine Barton's descendant, the present Lord Lymington. Disturbed by this impiety, I managed gradually to reassemble about half of them, including nearly the whole of the biographical portion, that is, the 'Conduitt Papers', in order to bring them to Cambridge which I hope they will never leave. The greater part of the rest were snatched out of my reach by a syndicate which hoped to sell them at a high price, probably in America, on the occasion of the recent tercentenary."

For more info, see this Newton Project page: http://www.newtonproject.ox.ac.uk/history-of-newtons-papers/...
Personally I never found the heavy IDE approach compelling and I'd much rather just build up a Makefile than rely on what VS and co are offering. MacOS used to be better in that case because you had native POSIX on top of a machine with excellent driver support and good ergonomics.

But now the winds really have turned. MacBooks turned to crap, Windows laptops improved and we have WSL with perfect VS code integration. I recommend anyone to try WSL, install VS code, install its remote extension and then go to a git repo in bash and type "code ."

It's magic...
They do use native apps, because they offer these features and other conveniences only afforded to native apps within Apple’s control.
From what I understand, with this new commit protocol they managed to improve response time of a writing transaction by shifting some work of determining its final status to the readers. Am I understanding correctly that readers' performance will degrade by the same amount?

While this is an achievement which some scenarios will definitely benefit from, like bulk loading or updating secondary indexes as mentioned in the article, what about other scenarios where read performance is more important, like the ones where there are much more readers than writers? Shouldn't there be a configuration option which commit protocol to use?
Picking Postgres for alternative applications such as pub/sub services also simplifies both deployment and development. You'll already be using Postgres for persistence, so why waste time deploying another set of services and develop another set of clients just to get the same functionalities?
These are notes from a live presentation at the WebKit Contributors Meeting. All the items were explained live, there is only so much the notes can convey.