skysight-inc/HackerNews huggingface dataset:
I don’t think tax avoidance is a good argument for anything. Do we really want to be encourage millions of young workers that avoiding tax is OK?
In computer spec alternate reality "HD" is 1366x768, HD+ 1600x900 and True HD 1920x1080.
I guess I'm also as guilty of looking at input/output rather than implementation here.
> Errors like the following one however are very hard to
> fix in case sensitive languages like C++ and probably
> even Rust

No, in Rust the compiler will emit a style warning if you have a function whose name includes capital letters. This can be toggled off (and also elevated into a hard error), but it's always on by default.

Furthermore, when you import a module Rust keeps it namespaced under the module's name, so you never need to worry about names accidentally colliding or being unsure as to where a symbol comes from. You have to use an explicit glob import to pull in all of a module's public items into the current namespace.

Furtherfurthermore, Rust warns when you import a symbol and then don't use it, so even if you name all of these functions differently and ignore the style warnings and glob-import the modules, then you'll get yet another warning when you fail to ever use two of the symbols.

Furtherfurtherfurthermore, Rust doesn't allow symbols with the same name to exist in the same namespace, so even if you went back and fixed all those functions to comply with the style warnings, you'd get compilation errors if you continued to glob-import any of the two of them.
Much of the YouTube content has auto-generated subtitles, i.e. Google is running their speech-recognition software on the audio stream and then using that to caption the video. If you used that as your training set, you're effectively training on the output of an AI. Which is kind of a clever way to get information from Google to your open-source library, but will necessarily be lower-fidelity than just using the Google API directly.
Moving past the hate in the community – Coding with Empathy
Wait a minute, people doing this with projector where using DLP projectors, do you need a OLED smartphone then? Because as far as I know, most screen emit light on black. Or is it reactive to a specific color. I have some doubt about the quality of the printing.
The amount of business traffic from boston to some place that isn't heathrow is miniscule compared to NY-heathrow.
es6 has one
This has the same problem as hyperloop, then. Sure the main part of the journey is quicker, but if you have to take a connecting flight from New York to Boston, and a train from Luton to London, it's overall slower than a subsonic plane.
Unzipped, the source code for GNU coreutils is 30MB (zipped 4MB). This is a great example of a collection of single purpose functions you should never rewrite yourself. There's only one dependency if you want to use them because they're packaged together. With normal desktop code, 30MB doesn't really matter and you can link only what you need. Can you do that with the usual Javascript package managers/bundlers, or would you need to send the whole 30MB package to the client to use one function from it?
I'm not sure if you're saying this of my comment or the OP, but I code professionally every day in this style and it's working out just fine. And the smaller my modules get the better it seems to work.
Worse yet, a backdoor or legitimate bug in any of these module could leave huge exploits in the entire Node.js ecosystem.
It's a lot easier to diff if you invented the originals.
Yes, but it's trivial to pin your dependencies exactly. That's not a reason to avoid small modules.
Raffaello D'Andrea TED Talk – Meet the dazzling flying machines of the future
To get an idea of scale, the mining operations can be seen on the satellite view of West Virginia on Apple Maps… even when the whole state fits in the window.
Rebuilding for most cases seems silly to me.

I've been working on a .net web app, that's been around since 2008. It's been continually evolved, so it's running on the latest MVC framework, uses microservices etc

As result it's build up a huge amount of automated tests. The business logic has been built up from experience and is well tested even for odd cases.

You throw away a lot of stuff for a rebuild.
Cartoons from XKCD creator will appear in high school science textbooks
At first I was a little surprised that we were comparing smartphones to cars to CPUs to...oceans. But then I remembered I'm on Hacker News.
We were using an external vendor for our production database (I've changed this now) and I was poking around their management console one morning when I notice something (I was about two months into this gig). The CTO walks into the office at that point and I ask him: "Hey, I can see that the staging database is being backed up, but the prod database doesn't have any backup files. Where are the backups for prod?". His response: "Press that manual backup button immediately, please." Turns out that production had been running for nearly three years without backup actually running...
The Apple-FBI Whodunit: Is Cellebrite Helping the Feds Crack the Locked iPhone?
It should, but the ECMAScript spec doesn't have it, and Node.js team prefers to keep the core libraries to a minimum and definitely do not want to modify prototypes. Thus we depend on userland to provide those features for us.
> You seem to be implying that the current minimum wage system is effective in some way. Try living in any city in the US on minimum wage...

You're talking about a completely different thing, unless you're advocating tipping everyone you believe may be on minimum wage.

At no point did what I write imply the current system is good, I simply said it exists and that the restaurant industry carved a special little exception out for themselves. That exception was carved out so they could directly push the burden of paying employees on the customers while continuing to get the same profits from their product.
> Has the project grown so large that it's starting to run into real-world performance issues?

oh-my-zsh is noticeably slower than prezto on multiple 'high end' machines I have with the same 'capabilities', i.e. plugins that provide the same feature set on both.
Nice! Curious how it compares to amazon's avs that went public this week.

https://github.com/amzn/alexa-avs-raspberry-pi
Text2Image: Generating Images from Captions with Attention
I once received advice on smalltalk that's been interestingly useful.

The advice was to ask questions could be answered with a number. Like "How long have you lived in New York?" or "How many siblings do you have?"

On the surface those don't seem great at stimulating conversation, but people seem to automatically expand on the number they give since they feel it deserves explanation.

I've used it several times when I've been set adrift at a cocktail party without a conversational thread to pull on.
Finding this module on NPM or npmsearch.com is pretty trivial compared to ensuring you implement this in a way that catches every edge case.

> It manifests in much slower bug fixing

I don't buy this at all, because I've done it myself many times. If you're waiting on a PR from the original repo owner to fix a Production bug, you're doing it wrong. It's trivial to copy the dependency out of node_modules and into your src, and then fix the bug yourself. Then when the owner accepts your PR, swap it back in. I don't understand the problem here.
Why we don't have an SST flight today
I don't know the first thing about how a business in the space operates. Can someone fill me in on why a startup like this would go through YC? How are $120k and Silicon Valley connections going to help a startup in this space in the slightest?
Apparently 'text' means something other than SMS these days?
What's with these kids and their "calculators". Back in my day we used a slide rule and we liked it!

But seriously this is stupid. Programming shouldn't be the goal. Just because you can write a function doesn't mean you should. Every line of code you write is overhead that must be tested and maintained. I guarantee that if the author chose to hand roll code instead of using packages he'd have a lot more bugs. But he wouldn't know that until he hit some mundane edge case scenario in production.
It did teach me how to understand a terminal / prompt. A few bits of information here and there and you suddenly feel happier because that part of the system also work for you.
It's amazing what Microsoft thinks are my "fave apps"... Kik? Really? Never even heard of "GroupMe"
It's considered "deeply flawed" by one (rather famous) cryptographer. And by "deeply flawed" he meant [1] that if the attacker has 2^64 plaintext/ciphertext pairs, he can then attack ciphertext 256 times faster than by bruteforce.

The relevance of this "deep flaw" to a realistic attack is unclear. (The attacker will need at least 0.25 zettabyte storage for those plaintext/ciphertext pairs - and don't forget about the time and bandwidth for obtaining them...)

TL;DR: GOST 28147-89 is an old cipher. You shouldn't use it today because there are newer and stronger algorithms available. But for its time, it was a brilliant algorithm, and attacking it still requires NSA-level resources.

And if you are interested and can read Russian, see [2] for a summary of known ways to attack GOST.

[1] http://eprint.iacr.org/2011/211
[2] https://ru.wikipedia.org/wiki/Криптоанализ_ГОСТа_28147-89
Going down the "lots of tiny modules" route is about these three things:

a) No standard lib in JS

b) JS is delivered over the internet to web pages in a time sensitive manner ... so we don't want to bundle huge "do everything" libs. Sometimes its convenient to just grab a tiny module that does one thing well. There isn't the same restriction on any other platform

c) Npm makes it really easy to publish/consume modules

d) And because of c) the community is going "all in" with the approach. It's a sort of experiment. I think that's cool ... if the benefits can be reaped, while the pitfalls understood and avoided then JS development will be in an interesting and unique place. Problems like today can help because they highlight the issues, and the community can optimise to avoid them.

Everyone likes to bash the JS community around, we know that. And this sort of snafu gives a good opportunity. But there many JS developers working happily every day with their lots of tiny modules and being hugely productive. These are diverse people from varied technical backgrounds getting stuff done. We're investigating an approach and seeing how far we can take it.

We don't use tiny modules because we're lazy or can't program, we use them because we're interested in a grand experiment of distributing coding effort across the community.

I can't necessarily defend some of the micro modules being cited as ridiculous in this thread, but you can't judge an entire approach by the most extreme examples.
In what way is a waiter's service different from a supermarket cashier's service or your dentist's service? All I am saying it's totally arbitrary that among many service professions only for waiters tipping is an essential part of their income. Sure you can tip your plumber but even without tip he will earn good money.
>> Although I was director, engineering was basically under the control of product and upper management.

IMO if you're the lead of the engineering organisation then you have the responsibility to convince your CEO when you feel you're right. As director it comes with a responsibility to do some politicking.
Red

export PS1="\[\e[31m\]\u\[\e[m\]\[\e[31m\]@\[\e[m\]\[\e[31m\]\h\[\e[m\]\[\e[31m\]:\[\e[m\]\[\e[31m\]\W\[\e[m\] "

Orange

export PS1="\[\e[33m\]\u\[\e[m\]\[\e[33m\]@\[\e[m\]\[\e[33m\]\h\[\e[m\]\[\e[33m\]:\[\e[m\]\[\e[33m\]\W\[\e[m\] "

Green

export PS1="\[\e[32m\]\u\[\e[m\]\[\e[32m\]@\[\e[m\]\[\e[32m\]\h\[\e[m\]\[\e[32m\]:\[\e[m\]\[\e[32m\]\W\[\e[m\] "

As always you can tailor them if you prefer different things to be different colors, I'm often lazy and don't change local machines to green but always change staging to orange and production to red.
In 2010, I was considering getting into Android development, so I paid full price for an unlocked Nexus S when it came out (I think it was about $500). At about the same time, I bought an iPhone 4 for my wife. That Nexus S became slower after each upgrade until it was nearly unusable. The UI was so janky that making or receiving phone calls was difficult, and wasn't even worth considering using the browser. The iPhone 4 stayed just as good as the day we bought it and my wife didn't bother upgrading until the iPhone 6S.

My current phone is a $200 Moto G and I'm perfectly happy with it. Lollipop runs well, battery life is good, and with a cheap SD card I don't have to think about storage. It isn't as nice as the iPhone 6S, but the Moto G is great value.
It's a hard problem, not an impossible problem. Naval ships would have code books distributed to as recently as the 1970s.
1000% performance improvement for intensive react apps
I totally agree. The npm ecosystem and the generally accepted practices in js these days come close to the bash style of composing & chaining a bunch of solid, specific little programs together to solve problems trivially that would have been a bear to do in many other platforms like java, C++, etc. I cringe at the idea that you should find yourself implementing l-pad in 2016, at least for the vast majority of projects that a typical engineer will encounter in their career. A similar case can be made for something as small as "is positive integer".

While I agree, there are two counter arguments:

1) As noted in other comments, this is a reflection of the core libs of javascript not covering enough of the basics. This is a subjective thing when it comes to where to draw the line, but wherever the border lies between "core" and "community" libs, on the other side you start running into things like "L-pad" and "Lib-L-Pad" and "L-pad2". If there's a great enough fundamental need, you experience a lot of crowding where lots of people offer up their solution to this, and reconciling that across larger dep. chains that disagree on which one to use can become a real burden.

2) Have you ever had the conversation with an auditor (PCI, HIPAA, etc) that your application is actually built on top of a huge substrate of software written by unaffiliated 3rd parties? And that between your own iterations you could easily have different versions for any/all of them? It's a difficult conversation. Much less the explanations to QA about why a build failed because lib X was updated to a new hotfix version in the 14 hours since yesterday's build, after a couple hours of wasted time of initially suspecting your own diffs, and trying to navigate through all the indirection between the actual stack trace and what actually caused the blow-up...
Historically, that's been the bigger issue. Or at least, that's what I get from Bamford's books.
I think it's likely they would have kept the code that valgrind didn't like if it was not a violation of the C standard. I don't understand why you completely reject that as a possibility.

I don't blame all problems on C, but I think it should be easier to write valid C. Dealing with uninitialized variables was just an example of something that could be changed. It wasn't supposed to be the biggest most horrible problem with C.

Compilers may not turn functions that hit most kinds of UB into { return; }, but they can. As a general category, that's a bad thing.
Is $15k a weirdly low number for this, given the importance the FBI has attributed to it? Anyone with similar contracting experience who can comment?
I am late 20's and I have no idea what you're trying to convey.

I weep for the future of coherent conversation.
because everyone would stop using it in a week when the next one arrived
The problem with this is: billable hours are what make you money, not working in the product.

Juggling those becomes very difficult.

I've been following this space for years, and there are no easy answers.

I think the model where the 'secret sauce' is proprietary, and you give away the infrastructure, like, say, Ruby on Rails, seems to work ok. Produces some good open source software and is still an 'easy'/straightforward business model, because you're selling a product.
.... isn't this a problem with node, and not developers? Wouldn't you say this is a symptom of a systemic problem of the framework that it is lacking common features that everyone needs?
Show HN: See the latests Swift open source releases in your OS X status bar
That'd be an awesome extension of the resources they invested, but it runs the risk of designs serving too many masters (like the F35 Joint Strike Fighter trying to add VTOL, making the non-VTOL thing way too heavy), and the A-series probably doesn't have enough cores for the unit price to work well for these services. What Intel is doing with Xeon Phi and the 18-core Xeons is the way things are going I think.
I didn't read it that way at all. He's calling out that Apple isn't doing a great job supporting the web and this fact is so important to him that he's willing to switch platforms.

And 'blaming the poster' is classic victim shaming. Not reading a post and then flaming based on the title is exactly what the web tends to do far too easily (and what we need much less of)
I've always been a Debian/Ubuntu guy, but the Redhat folks are good people and have continued to dedicate a lot of resources to open source software, through thick and thin.
That's incorrect. This is a Google Cloud Platform service and when it reaches General Availability (GA) it will be subject to our Deprecation Policy. Just like Compute Engine, Cloud Storage, etc. requires us to give at least a 1 year heads up.

Disclosure: I work on Compute Engine.
Nexuses seem to have about a 3-4 year update window.
Oh, that's probably true. Not all species will adapt, and as the niches get refilled things will be chaotic.
> In my opinion, if you cannot write a left-pad, is-positive-integer, or isArray function in 5 minutes flat (including the time you spend Googling), then you don’t actually know how to code.

Spoken like someone who writes functions in 5 minutes that I find bugs in later.

Just because a problem is simple to describe informally doesn't mean it is simple to implement without bugs.
Worse yet, the OS is compromised. This is why I hand roll all my encryption libraries. /s
I read it. I'm just talking about the headline - it's something you see attached to serious articles.
Google explains its cloud computing vision for enterprises and startups
"all pieced together. fragmented applications and processes that dont work side-by-side with eachother"

Wow this is... don't even know what to say here. Just... incredibly superficial. Let me put this puzzler to you... I want to share something (say an image, video, sound, URL whatever...) from inside an app to a friend via a chat app. Compare how that's done on Android vs in iOS. If you don't know what the answer to that question is in Android, please refrain on commenting about what platform feels like a bunch of fragmented precious snowflakes glued together on a rectangular screen.
I have a buddy who was super high up in a telecom back in the late 90s/early 00s and he mentioned that all the big telecoms basically voluntarily were creating traffic backdoors for the government.

When he mentioned it, he didn't even blink. It was eerie.
تطبيق+القفل+اب+لوك+AppLock+مع+توفير+طاقة+البطارية+برابط+مباشر
Cellebrite's entire business is building these kinds of exploits into its shrink-wrap software sold to thousands of law enforcement agencies, including po-dunk municipalities that presumably can't afford federal government contracting rates. I'd guess that if they're quoting $15k, they're going to run the software they already have.

They are not know to be effective against current iPhones, but they do advertise their ability to break all Androids and older iPhones via USB on their public website.
Google plans to bring its enormous-scale data center know-how learned fulfilling 85% of the world’s searches with open source software in a serverless secure cloud in which it invested $10 billion in capital equipment last year. It has repurposed open source versions of its highly optimized internal systems used to build and operate the seven services such as Maps and Gmail that have more than a billion users for its cloud.﻿
Maybe this was the sum quoted by Cellebrite.
What's the problem of writing a function with a few lines of code and exports as a module?

I think it's totally fine. Like other people said, it's the mindset we borrow from Unix, do one thing and do one thing well. The function would be well tested, and could be reusable.

I don't understand why so many people just require lodash into their project (when they start project) while they only use one or only minimum set of the functions. I mean lodash is a very great library with clean and well tested code, but it's also quite bulky like a big utility lib, and for me most of the time I only need one or two of the functions I would just go to npm and find a module just do that thing.
Wow, I feel like I could have written this. Back when I used Python, I had a folder full of functions I would copy-paste between my projects. (And maybe some of the projects contained unit-tests for the function. I didn't always keep those tests in sync.) Updating them was a pain because inevitably each one would get slightly modified over time in each project separately. Eventually, I bundled all of them into a bundle of completely unrelated utility functions in a folder on my computer somewhere, and I would import the folder with an absolute path. Sharing the code I wrote was a pain because of how much it referenced files on my local computer outside of the project. I never considered publishing my utility module because all of the stuff was completely unrelated. I'd rather publish nothing than a horrifying random amalgram that no single project of mine was even related to all of the subject matter present in it.

With npm and the popularity of small modules, it was obvious that I could just cheaply publish each of my utility functions as separate modules. Some of them are about a few dozen lines, but have hundreds of lines of tests and have had significant bugfixes that I am very happy that I haven't had to manually port to dozens of projects. I don't miss copy-pasting code across projects, no matter how many claim I've "forgotten how to program".
They should call this tick-tock-tack, since the last stage is when they tack and introduce new architecture. You heard it here first.
SOPA hypocrisy in gif-laden House Judiciary Committee press release
Noticeably slower at doing what? I haven't noticed any issue, but I'm maybe a bit naive; I rarely use the shell for anything that isn't near-instantaneous and isn't just waiting for some other process to complete (e.g. curl, compilers). For more complicated stuff I usually write something in a scripting language.
- Government isn't about morality.
- Really? What is it about?
- Stability! Keeping things going. Preventing anarchy. Stopping society from
falling to bits. Still being here tomorrow.
- What for?
- I beg your pardon?
- What is the ultimate purpose of government, if it isn't for doing good?
- Minister, government isn't about good and evil it's only about order, or chaos.

https://www.youtube.com/watch?v=A-pj3mBscgo
Thanks for the link. Neoreaction seems superficially similar to Marxism, in that it makes some interesting criticisms but would probably lead to millions of deaths if actually implemented.
> There's the infamous story about how Target knew a teenage girl was pregnant before her father did.

> AT&T just sent me a letter saying they're giving me an extra 5GB/month bonus data as long as I keep my plan, which I assume happened because their data indicated I was a risk for downgrading or switching carriers.

This isn't Artificial Intelligence though. These seem like they fall under 'Reactive systems' or 'Data Analytics'.
If you sign up you can scroll down and see the pricing on https://www.speechmatics.com/account/