skysight-inc/HackerNews huggingface dataset:
In a few different cases (one node, one browser-based) I've had medium-sized read-only datasets of a couple million objects where I've tried to conserve memory by using typed arrays. While it saved a good amount of memory, property access was significantly faster via objects than typed views. I'm curious to re-run the benchmarks with Turbofan though, maybe things have changed.
That's a very cool idea, but the spam filtering of gmail can hardly be matched. On the plus side, now you could send emails with much larger attachments.
Don't forget the red box, which you could make by replacing the 3.579545 MHz crystal powering the chip that the OP reverse engineered with a 6.5536MHz one, and then the top row and bottom column tones become 1700 / 2200Hz to simulate the pay phone nickel / dime / quarter tones.
in the first paragraph the author addresses this directly. The author suggests this may be suitable for smaller projects

> Webpack is a crucial tool for building sophisticated, highly optimized web applications, and is encouraged by many influential web developers.

However, for newer developers, or those working on less ambitious projects, Webpack mostly occurs as a barrier
It's great to get to read Ellen Pao's perspective. Most of this is not news to us, but the brigading in this thread is strong. It seems like many men see this kind of sexism as just normal behaviour.
Very good article, by the way.
The line has blurred because many companies now mandate that you hold a degree and 22 years of experience to even look in the direction of a computer, but I would say that not too long ago, it would be a pretty fair claim.

There's no need to pretend that code monkeys who churn out generic CRUD programs are highly skilled or talented. It's respectable, pays enough, demands enough, and many people are capable of it; it's as close to a blue collar office job as you could ask for.

Actual software "engineers," working on complex problems in computation, mathematics, physics, etc. are hugely outnumbered, even today, let alone tomorrow.
Something tells me no one is paid but Oreo benefits with free advertising for their cookies/biscuits
Do you find you have problems delivering to other mail servers?

That has always been the trick. Running the mail server is easy. Having your email show up in other servers is "hard". Right now, with so many users using GMAIL, using gmail is a huge boon to not being marked spam (Google is way less likely to market a @gmail.com email as spam compared to say a @aol.com email).
I can't imagine how people depend so heavily on free accounts from Google. Which notoriously ignores help requests. And typically don't retain backups. Seriously?

But bottom line, it's Google's business what they do. And with a free account, there's no recourse. Except maybe getting to HN front page, and reaching someone sympathetic at Google.
An accident that they even shut down his blog? Perhaps a mistake, but definitely no accident.
Are We Different Writers When We Move from Longhand to a Screen?
are there any antifa sites being blocked or denied service? don't they incite violence in the name of ideology?
light-weight multithreading that enters a scheduler loop when I/O would block is great, and I haven't seen any advantages of async/await compared to that, other than ease of implementation (you make the programmer or library author implement multithreading, rather than implementing it in your runtime).

Promises are at least slightly more interesting because they can functionally compose in various ways (but most of the time it's just a dozen then() calls in a row, and threading would have been better).
Fairly obviously a licensing/marketing deal.

"The world's favorite cookie" right in the first caption.
Almost subliminal images of Oreos in the background as you scroll.
Life is very difficult here. And no one thinks of themselves as a villain. Villains especially.
> Allocation in modern generational GCs is in a completely different performance category than C-style malloc is.

Yes and no. If enough allocation happens that a GC pass occurs while you're still running your JS hot loop you're pretty much screwed and all your performance vanishes. If you want to see this in the extreme go open an Android systrace or Chrome chrome://tracing trace result and do a JS profile while you do so. The single largest consumer of JS CPU time is the GC at nearly 13%.

The problem with modern generation GC langauges is they tend to be designed assuming that allocation is always cheap/free and it just isn't. That's a fairytale. It's just not true.

Also just because it only takes 6-13ns for an allocation to be given to you doesn't mean anything when the first access of that allocation is a cache line miss compared to if you did the same thing in C and it was on the stack, which is likely sitting in hot L1 primed and ready to go. Reusing the same memory address range is critical to getting maximum performance, and modern generational GCs are miserably bad at that.
Typically the claims of heavily improved single threaded performance are "up to x% faster", and the only time you see those peak performance improvements are during uncommon benchmarks.

Until full reviews come out it's hard to say how much of improvement across the board we'll see, but recently 2-3% ipc improvement on average plus whatever boost to frequency seems to be standard per release.
[I'm a cofounder at Hack Reactor, a coding bootcamp.]

Your comment defines a trade skill as one "that most anyone should be able to learn in several months without a general STEM education". So, let's evaluate that question for a few different trades/professions.

"Software Engineering": We have determined, through experimental proof, that bootcamps can make (some) novice non-degree-holders into employable software engineers in 3 months. Probably 3-18 months would cover most people that would otherwise be entering college in a CS major.

At parties I like to ask people how long it would take to teach someone to do their job. (Posit that they're smart and interested.) For most white-collar jobs, people answer "6-18 months". Most trade schools are somewhere in that region as well.

In my opinion, most professions would be well-served by the bootcamp model (like software engineering is) and a 6-18 month training period. So per your definition, I would say there are few professions out there, if any.
If it matters what the user's username was or what button they clicked or what form they're on --- to the business --- then sure, describe those in natural language specs. If they only matter to the implementation, they should be in the implementation's integration spec suite (which, discussing technical detail, is not likely to be consumed or produced by business, and so has nothing to gain from being written in natural-language, can simply have natural language comments as you mention.

You shouldn't e.g. try to get to any coverage level with only a NL story suite, etc., that is a gross misapplication.

NL Story suite has a very simple utility: the customer can read them and say "yeah, this is an example of what should happen" or go "no, that's not quite what I meant" early on, before implementation. Being able to automate testing of that document as validated by the customer is just a bonus. 90% of the value happens before any code is written. If you are writing an executable natural language story and have no customers to read it, or if you are covering details they will glaze over while reading because they can't imagine or validate what is described, then you're using the wrong tool.

edit: Even a suite in code, for technical users, should strive to have more reuse than having each test describe exactly what actions are taken, since that's too hard to maintain. If your tests aren't DRY, you spend too much time updating the 50 places your login form selectors are reflected in the suite and the test suite acts as scar tissue that prevents changes instead of a protective but flexible skin and skeleton that helps the program adapt.

Over-using story tests and dealing with the maintenance burden / poor abstractions, overly-repetitive integration suites that make changes hard and inappropriate use of unit testing that makes refactoring difficult are all really common traps when people don't get the big picture of test automation, but they are entirely avoidable. A test suite is like any other piece of software and has to be designed (and factored) for the reality that its behavior will change.
Exactly, back up a few years and it was still a buggy and bloated slow piece of shit. Which is the reason why Google decided to go with Python in the 90's when Java was the original language their search engine was written in.
"new emoji" is an OS-level feature now. Welcome to 2017.
Ellen Pao 'resigned' because she displeased too many people. Her style was a little too autocratic for the Reddit culture. For instance and if I recall correctly, telling the 'Ask Me Anything' moderator to move to video interviews and then firing her when she refused. Pao instructing the entire Reddit team to upsticks and move to the one city.
...But if, for the same input, it always tries the same candidates in the same order, then it is deterministic.
Supposedly the carriers are real pains as well. I've heard horror stories of months-long approvals processes on Verizon and AT&T ROMs.

It's a game I wish they'd get out of entirely. There's no such thing as a useful carrier overlay.
At first I thought so too, but the brand dilution that is going to happen has to have some negative penalty.

Oreo will receive "free" marketing, but now will have to share the name with a version of a mobile OS.
Ignition/Turbofan has a new IR - IRHydra 1 and 2 won't help. For Turbofan there's https://github.com/v8/v8/tree/master/tools/turbolizer .
I don't like the product placement in the release name.
Despite being successful for an academic, he's not exactly a famous psych prof at the level of say, Steven Pinker. Before politics collided with his work this year he didn't seem to be politically active at all, either.

It might have changed a bit after Joe Rogan's podcast but to be honest, most people outside of Canada probably have no idea who Jordan Peterson is.
> It was directly related, because it threatened Microsoft's OS monopoly by providing platform independent content

It's related to Microsoft's notice for illegally leveraging their OS monopoly, because of a speculative future threat it posed to that monopt by commoditizing the underlying OS.

It isn't directly related to the market at that time in which Microsoft had a monopoly; competing browsers we're not yet substitute goods for Microsoft's PC operating system, the way that competing email services are substitute goods for Google's email service.
Europe still has Lèse-majesté laws in the 21st century:
https://en.wikipedia.org/wiki/L%C3%A8se-majest%C3%A9

Not to mention the Holocaust denial laws. But you can deny Armenian genocide just fine. Convenient, eh?

"To learn who rules over you, simply find out who you are not allowed to criticize." -- Voltaire.
They did, of course. Little known fact: Google is one of the largest tenants in Chelsea Market, which used to be the factory were Oreos were first made.
I wonder who paid who..
"Before the Internet existed?" You make that sound like such a long time ago!! Meanwhile I see there's another Ycombinator news item in which someone discovered the "HERE IS" key on Teletype ASR-33s (which I believe one pressed to automatically read the already-punched papertape with the code to identify your "Station".) Again from pre-Internet days when mighty dinosaurs still roamed the earth writing games on Teletypes on IMSAI-8080 computers and pirated copies of Microsoft 8K Basic.
I doesn't look like that stopping time is user-defined, it's a compiled in constant.

Given that, I don't see any reason why the algorithm should be non-deterministic just because it gives up after a set number of iterations. As long every time it sees a given string it tries the possibilities in the same order, scores them the same way, and stops at the same place then it should be deterministic.
> However, I recently started using async/await in TypeScript, and the result seems to be try/catch statements everywhere.

Why do you have try/catch everywhere? Unless you're actually going to handle the error, you shouldn't do anything as it will bubble up till it gets to a piece of the app that can handle it. For web apps a lot of the time that's a single request level handler to return a 5XX.

> Code using async/await seems to be more verbose and unruly than just sticking to Promises, which I now appreciate the elegance of much more (callee convenience/error delegation).

Eh? Besides the addition of the "async" keyword on the top level function, it's always less verbose.

Where I think things get a bit tricky is awaiting the composition of Promises to support parallel processing (as opposed to just 1) await foo() 2) await bar() ...). It's best to treat that like regular composition and simply await the result.
Why on earth did they go with a restricted trademark, Oreo?

Oreo must have payed a good sum of money I suppose?

Coming up with the legalese on how and where Google is allowed to use the Oreo trademark seems difficult.
systemd, Wayland and Xorg are switching too.
For those not familiar with the fox/hedgehog analogy the parent is using, it's something Isaiah Berlin originally wrote about: https://en.wikipedia.org/wiki/The_Hedgehog_and_the_Fox
Pick one : https://github.com/facebook/react/wiki/sites-using-react
At the moment, there aren't a ton of real-world use cases aside, but the future will be very different!

Check out Open Bazaar for an entire market place that's facilitated via cryptocurrencies.
I have one question that I am interested in knowing. Can someone fork React, change its name, remove patents + bsd, and publish it?
It sure beats giving out your cell phone number on the internet for people to contact you.
Just because you've finished a machinist apprenticeship doesn't mean you're a master machinist.

It's the same thing for software development. You can learn how to be useful or productive (albeit with a limited set of skills) in several months of applied training. That doesn't mean you're automatically skilled in things such as handling big data, compiler construction, HPC/optimization, systems programming, multithreaded applications...the list goes on.

However, as far as I can tell, not only is a 4 year program overkill for what most people want to do, a CS bachelor's degree usually doesn't cover particularly relevant information. A computer science degree teaches computer science, not software engineering. It's intended to introduce basic concepts which will be needed when proceeding on to do research.

What most people really want is an education in software engineering.
Bioinformatics scientist here.

1) There are lots of brilliant people in the field, but it is also the degree that dumb people who want a science degree or are "pre-med" get. It tremendously lowers the value of my undergrad degree. If you look at high-paying jobs (finance, investing, etc), you'll often find people who say they occasionally hire in a bright scientist who wants to switch industries. They typically hire physics and chemistry majors and are much less likely to hire someone with a biology degree.

2)The computational biologists/bioinformaticians/etc in this field are pretty variable in their CS skills and a good deal of the top performers leave the field because pay is really, really terrible. (ie my compensationv is 65K, high COL area, MS required, 1 year of direct experience under my belt, plus an additional 4 years of experience in the wider biotech industry - trust me I think my life is a joke too).
>So yes, it will make code easier, but I fear that will only serve to prolong the dominance of what is arguably the wrong programming model/architectural style.

Nested callbacks and even Promises are not the "right model/style" by any measure. Even 30+ year old languages had better answers to asynchronous programming than that.

Nested callbacks is so backwards its like writing in assembly. Only people whose first exposure to asynchronous programming was Node think it's a valid programming style.
PeerGrade - https://www.peergrade.io/blog/peergrade-goes-y-combinator/
Not like you're five, but if you're interested: the standard introduction is still 'Partial Evaluation and Program generation', which is freely available
http://www.itu.dk/~sestoft/pebook/pebook.html
> that programmer has to manually specify where he wants to make asynchronous vs. synchronous functions to get the optimal performance.

programs aren't just pure computations. There are plenty of times when you want a specific event to happen at a specific time (as in, wall-clock), and plenty of times when you don't care when something computes as long as you end up getting a result at some point.
> I wish one of the Googlers reading this here could reach out internally what is going on here.

Or better yet:

1) move to a reputed, paid e-mail account (fastmail, mailbox.org, tutanota, protonmail etc...)

2) there used to be baywords.com for uncensored blogs, but I think you can trust posthaven.com.
>the supposed infiltration of Marxism into culture and ideas like White Privilege and Cultural Appropriation

You can't argue that "white privilege" hasn't infiltrated culture. An alarming amount of people have openly disparaged white people when talking to me, even though I am white myself.

If you're not white, it's almost socially acceptable to say "fuck white people" in cities like SF, NYC, and Chicago. I think it's horrible and I think Peterson is right.
"Before we proceed, please provide a clear, coherent, short summary of what you personally believe Damore's argument is, and then agree to personally commit to that belief for the duration of debate."

Do that.
In case of 4.4 KitKat it was the idea of Nestle's advertising agency, J. Walter Thompson [0]. It was novel at the time, and it as more than just jumping on the letter "K", because it tied the "have a break, have a kitkat" line with the idea that people reach for their smartphones when they have a break. Now I imagine it's just people in suits negotiating the deal for the next release name.

[0] https://jwt.co.uk/work/android

Disclosure: I have worked for a JWT subsidiary at the time.
If it supports prior services like Google cloud print, perhaps even uncertified printers could work
This link from the other thread has a lot of solutions for different options. The Switzerland based options seem pretty promising.

https://www.privacytools.io/
True. That's a totally different problem that Treble isn't intended to address, as far as I'm aware.
Most of the stuff he wants is either trivial, or an implementation hell that Will never happen. Hard and soft links solve the hierarchical filesystem problem, kwin has windows tabbing (nobody uses it), rewriting every single app from scratch for a theoretical gain? Sure that's happening.

The only good idea is the system documents database, and it isn't really that useful.
A lot of people complaining about using a brand name here -- isn't Kitkat (the 'K' release) also trademarked?
>That's essentially the main reason Node is any faster than Python.

v8's JIT is many times faster than Python in CPU bound tasks without any asynchronicity involved.
Finally Android will stop Facebook apps from sucking my RAM secretly!
All the spam filtering in the world won't help you after your account evaporates.
The lack of momentum will awfully hard to overcome.
Neat! Don't companies like Intel etc. still 'bin' chips into different products? Although I'm not sure if the reasons for binning now are different?
The language barrier and easy access to lots of capital in China.
I don't think so. Well before Rowhammer, Google published their paper showing the high amount of memory errors they get.

What's changed is higher memory densities, making it even more important.
There should be a live feed of our planet from space available online, on a TV channel globally, and on an app that does nothing else.
> Google has no special power to decide “illegal”.

They don't need to - that's been taken care of for them by the written law. Unpopular speech has yet to be considered illegal.

If the law enforcement disagrees with the service provider about providing a grace period, then law enforcement can get a court order. It's a small hurdle, but it keeps everything on the level.
For a person who is relying on benchmarks, you should know that benchmarks are only a rough indication of how well anything performs for a very specific use case.

Your reply is arrogant and ignorant, and you should feel bad about typing that.

> If you are that interested do your own tests.

Why is he not allowed to review your results or check what factors you benchmarked it on?
If there's no citation, that claim does not stand.
fintech is getting insanely huge in brazil right now.
Getting ready for Android Raiders, with doubled security through two fingers fingerprint reader.
Two, if you count ⊠. There was a nearly forgotten effort to define standard symbols for all the ASCII control characters — ANSI X3.32 aka ISO 2047¹ aka ECMA-17².

¹ https://en.wikipedia.org/wiki/ISO_2047

² https://www.ecma-international.org/publications/files/ECMA-S...
I know this is a non-issue for many, but those emojis look really dated. Every update they get harder and harder to read in small form. One of the things I observe, mainly on Instagram Stories is only people with iOS post with emojis attached, I never see Android ones. Too bad there is no way to install custom emojis in any system (without rooting/registry tweaking), like we do with fonts.
/Looks at price...

Gets you 11 Pi's ...
Gets you only 1 Intel CPU, no memory, motherboard, heatsink, fans.

Reminds me of the Celeron® Processor J3455... 10W rating on Intel there page. On AVERAGE! Then when you see the real power usage under load for MB + CPU + 16GB memory, its actually doing 35W.

Where as the Pi's are doing 3.7W max per piece. So even with 4 pieces to match the performance, your still half the wattage.

If Intel really scaled that good in power vs performance, why are we not seeing x86 phones all the time?
Pretty-printing is tough. That said, please don't reinvent the wheel. There is research that has gone into this that should make most of this stuff pretty straightforward. I personally recommend Wadler's "A Prettier Printer" [0] (although credit goes to Hughes for laying a lot of the groundwork [1]). It too uses an IR and has several possible heuristics for rendering.

I've been using an implementation of it [2] with a lot of success for pretty printing Rust code [3].

[0]: https://homepages.inf.ed.ac.uk/wadler/papers/prettier/prettier.pdf
[1]: http://belle.sourceforge.net/doc/hughes95design.pdf
[2]: https://hackage.haskell.org/package/prettyprinter
[3]: https://github.com/harpocrates/language-rust
After the last time Google shut down a random high-profile person's life (i.e. their website, their email, their account, etc), I immediately downloaded Thunderbird and got a locally stored copy of all my emails.

If Google shut down my account tomorrow, I think I could recover from pretty much everything else (although I'd have a hell of a time with the Android phone), but a decade and a half of emails are damn near irreplaceable.