skysight-inc/HackerNews huggingface dataset:
This is a strange argument. The `unsafe` keyword only lets you do the following: dereference unsafe pointers, call unsafe functions (which usually either dereference unsafe pointers themselves, or are just wrappers over C functions, which are obviously unprovable), and mutate static data. Saying that safe Rust is "barely complete" is just as good as saying that Python is "barely complete" due to the fact that it doesn't allow you to read arbitrary locations in memory.
reduce isn't a safe way to add floating-point numbers unless your accumulator is much more precise than your array values. You'll end up with what they call "catastrophic cancellation".

And they won't let you have fixed-point in JavaScript!
Anything at all would be better than the current chip-on-card with my visa credit card. Many terminal with the chip slot will sit there for a while and then say "swipe card". When it does work it seems to take forever. Luckily I've only run into one store, Home Depot, that demands the chip be used.
Rob Pike: "A little copying is better than a little dependency"
Aren't they planning to go to 7? I thought I read that somewhere.
I suspect that contract is unrelated. Details of the contract are visible at:

https://www.fpds.gov/common/jsp/LaunchWebPage.jsp?command=ex...

Specifically, the "description of requirement" says:

IGF::OT::IGF UFED software renewals for seven machines.

Which sounds like a routine license renewal... unless, of course, they're deliberately being misleading with that line item.
I'm readership.

I want to think about tech, but the right tech, the tech landscape, ecosystem, and tools that have to evolve to achieve my or my customers' mission.

Everything else, don't make me think. Don't waste my time. Toast my toast. Protect my data. Always work when I need, with no cognitive load.
Leaving aside all the advertisement and marketing.

JSPM -> sounds like a good idea until you try using it, and SystemJS is just sad. Its not the fault of the specs, its just that the creator is having difficulty with funding - as with any other good open source projects.

Webpack -> Slow, unstable and documentation is incomplete.

RollUp -> I am not going to listen to the author's comment on how awesome his product is -_-

I still think browserify is the only bundler out there that is sort of stablish.

I locked my browserify@4.0.0 for 3 years and recently moved on to browserify@9.0.0

Being in the JS world you need to be conservative these days - especially if you want to ship in time.
Ahh, so they're soldered on to the motherboard. I was just looking for that sort of form factor over the weekend (as a way of getting the low-power 6th-gen i7s... but didn't think to look for Xeon).

I will have to consider this. I run a Mini-ITX board in a Micro-ATX case anyway. Perfect form factor.
Yes, or more accurately a large new generation of coders is entering the workforce who know how to code only in a superficial sense and think this is a good thing.

Programming, and especially startup programming, is being taken over by people who are primarily technicians rather than engineers. They want to assemble prefab components in standardized ways rather than invent new things. They are plumbers who know how to install from a menu of standard components, rather than civil engineers desigining purpose built one-off aqueducts.

It is the inverse of the "not invented here syndrome." The technician-programmer is trained to minimize time spent thinking about or working on a problem, and to minimize the amount of in-house code that exists. The goal is to seek quick fix solutions in the form of copy/paste from StackOverflow, libraries, and external dependencies to the greatest extent possible.

In house coding should, they believe, ideally be limited to duct-taping together prebuilt 3rd party libraries and services. Those who want to reinvent the wheel are pompous showboating wankers (they believe); creating your own code when you don't absolutely have to is a self-indulgent waste of time for impractical people who just like to show off their hotshot skills and don't care about getting things done. Move fast and break things and all that.

This began with stuff like PHP but really got going with Rails, which preached convention over configuration as a religion, and supplied a standardized framework into which you could easily fit any generic CRUD app that shuttles data between HTML forms and a database (but is painful if you want to deviate from that template in any way.) Note that Rails doesn't use foreign keys and treats the relational database as little more than a glorified persistent hash table.

This set the stage for Node.js (why bother learning more than 1 programming language?) and NoSQL (why bother learning how database schemas work?)
The Anatomy of a React Redux App
Or you could have all the bugs introduced in everyone's hand-rolled implementations of it. I'll take multiple versions of the library instead. It's much easier to track issues and submit patches to update their dependencies later.
Perhaps it could instead be rephrased to 'the ability to build an internal model of their own, and other people's mind'?
The Netflix Story: Riding on the Wave
This comes up a lot when people discuss anything related to npm modules. It's easy to simply dismiss these trivial one-line modules as "insanity" and move on, but there's actually plenty of good reasons as to why many prefer to work with multiple small modules in this manner. This GitHub comment by Sindre Sorhus (author of over 600 modules on npm) is my favorite writeup on the topic:

https://github.com/sindresorhus/ama/issues/10#issuecomment-1...

TL;DR: Small modules are easy to reason about, and encourage code reuse and sharing across the entire community. This allows these small modules to get a tremendous amount of real world testing under all sorts of use cases, which can uncover many corner cases that an alternative naive inlined solution would never have covered (until it shows up as a bug in production). The entire community benefits from the collective testing and improvements made to these modules.

I also wanted to add that widespread use of these small modules over inlining everything makes the new module-level tree-shaking algorithms (that have been gaining traction since the advent of ES6 modules) much more effective in reducing overall code size, which is an important consideration in production web applications.
Of course they can, which is why perhaps apple "long suspected"... maybe shipping times were fucked and apple noticed - but my question is WHEN did apple notice???
I wouldn't mind so much if these micro-modules were written in a style of thoroughness; heavily commented, heavily documented with pre-conditions, post-conditions and all imaginable inputs and outputs explicitly anticipated and formally reasoned about. I don't mind over-engineering when it comes to quality assurance.

Looking at that left-pad module though - no comments, abbreviated variable names, no documentation except a readme listing the minimally intended usage examples. This is not good enough, in my opinion, to upload to a public repository with the objective that other people will use it. It is indistinguishable from something one could throw up in a couple of minutes; I certainly have no reason to believe that the future evolution of this code will conform to any "expectation" or honour any "commitment" that I might have hopefully ascribed to it.

[EDIT: I've just noticed that there are a handful of tests as well. I wouldn't exactly call it "well tested", as said elsewhere in this thread, but it's still more than I gave it credit for. Hopefully my general point still stands.]

The benefits of reusing other people's code, to a code reuser, are supposed to be something like:

(a) It'll increase the quality of my program to reuse this code - the writer already hardened and polished this function to a greater extent than I would be bothered to do myself if I tried right now

(b) It'll save me time to reuse this code - with the support of appropriate documentation, I shouldn't need to read the code myself, yet still be able to use it correctly and safely.

Neither of those things are true for this module. It's not that the module is small, it's that it is bad.

(True that npm's mutability is a problem too - this is just a side-track.)
given the tone of the rest tone of the article, it might have been tongue in cheek
IS has sent 400 trained and coordinated terrorists to Europe
Occasionally just opening the shell can be slow with oh-my-zsh. It can be a bit annoying (especially if you need a few more plugins). However I have not really noticed as much of a slowdown lately so perhaps it has been improved - I haven't really tested it, this is just my own perception.
Oh man, having to live somewhere the commutes aren't an hour long (or more) and you can afford a house, how terrible...
Well if I was interviewing the guy, my second or third question would be "tell me about these packages you published on NPM"

It's going to be damn hard to make an average function sound impressive.
It's completely subjective that you and the poster think "Apple isn't doing a great job on the web" - for one, I think they're doing brilliantly. Safari is extremely fast and well-optimised on iOS, certainly a better experience whenever I've compared iPhones and Androids of similar vintage side-by-side.

And I'm relieved that web gizmos like bluetooth support aren't built into iOS Safari. I can't think of a more inviting attack vector.
Neat! I had tried a project like this a few years ago as a way of measuring the perks and extras outside of the standard Glassdoor-esque metrics.

The tough part is that the ideal startup/job is different for so many people, and many of the things are subjective and hard to describe, so your best shot at getting quality data is to make sure you can encourage anonymous input, and then some sort of machine learning to turn all of that qualitative data into easily-digestible quantitative data.

Good luck and keep us posted on your progress!
Indeed.

I don't look at real-estate as an investment, but rather as a sunk cost. I need somewhere to live, I want to screw around with walls and plumbing fixtures when I feel like it, owning seems like the right option.

Of course you don't actually own your co-op, you just own shares in a company that actually owns your property.
After working with JS/Coffeescript/Python/Ruby for years, Go has been an enormous breath of fresh air for me. Of course it's all a matter of preference.
I still find it hilarious that, upon the bulk of SCM use shifting to a DVCS, the first[1] thing people did is run out to build a central hub.

[1] For the pedantic, it probably was not literally the first thing; I'm sure some folks went to the rest room, others ate something, still others took a nap.
3,000-Year-Old Chinese Oracle Bones Go 3D
I'd be interested to know what language it is.
A massive chunk of our engineers are (globally) remote. A lot of communication happens via mailing lists, many of which are the public upstream project lists. There is also a lot of use of internal IRC servers for more real time communication.

Outside of that there is also a fair bit of freedom/latitude for individual teams to do what works for them.
This is the right answer! You want a staging/acceptance/mirror environment that's the same as production, right? So make it with nightly restores of the production backups. You get a crisp, fresh staging environment, and regular validation of your backups too. Just remember to run full production monitoring against your staging environment too.
Sounds like you have a buggy or faulty device.
What is the web app language you use at work? I assume you're talking about something that runs on the client -- a web browser -- so it probably compiles down to JavaScript, right? JS literally has no numeric type that isn't a float, so how does your language escape this fundamental limitation?
But this doesn't address the author's point that each module, each dependency is an additional point of failure.
I was talking about wafers, not dies, but it's all speculation regardless.
>That's certainly true for Google or Amazon but not for most real corporate IT departments.

I can't speak for all corporate IT departments, but I'm at a very large corporation that certainly cares about idle power consumption. Over the years our servers have gotten more powerful, and more power hungry. It's not that hard to add more power, but adding new cooling isn't so easy. The less power we use overall, the less cooling we have to add, and the happier we are.
No it really doesn't. It is so far away from even Perl's printf (considered ancient by most JS programmers) that it is not even funny.
Echelon.

It is real.

It has been around forever.
does GNU coreutils include sed/awk?
They could do stuff like this for their own servers:

https://www.kickstarter.com/projects/designshift/orwl-the-fi...

But they may want to build their own chips, too, because they probably shouldn't trust Intel (they do some of that already, but they may need more powerful chips for their datacenters).
"Unfortunately, eliminating tipping can be complicated, and evidently can also lead to a higher tax bill…"

Any time on many forums where this is brought up a cadre of 'service industry staff' will show up and trot out lines about how they are "legally required to pay tax on a certain amount of tips, even if that's not what they make", when the reality is that "if they make less than that they should be able to show it" (and even that's not a perfect science, and still errs on the side of the server) by virtue of bank deposits (you can still keep some cash on the side).

But that "seems like a lot of work" to those people - why should they have to expend effort to document their (lack of) income in order to minimize their expected tax?

Nope... while service industry work is rarely glamorous, it's not that horrific. Unsurprisingly, those same people can often be found mocking people's ideas of tipping - apparently according to them, you should be expecting to tip 25% as a baseline these days... huh.

So if I go to Red Robin and my partner and I have a drink or two, and our bill comes out to about $60, and you have four other tables, all doing something similar, and we are there for about an hour, maybe a little more, you should be picking up $60-75/hr for tips?

Huh.

But "if you tip 15% or less, then I am actually having to pay to serve you because I have to tip out all these people no matter what tips I actually get, and the IRS demands I pay taxes on all these tips even if I make less"...

The reality is there's no requirement like that from the IRS - there's a base expectation, and if you can't provide documentation that you made less, that's what you'll be taxed. I wonder how many of these same servers provide that same documentation when they make -more- than the base?
You sound incredulous. It's a thing.
http://www.pcworld.com/article/2083300/report-nsa-intercepts...
Idea Deathmatch, new saving feature, unlock code: DR34DL0CK
Or have the encryption turn on a day after the phone is purchased...
Microsoft’s teenage AI shows I know nothing about millennials
There is nothing even remotely similar to Marxism about it (and it wasn't "the implementation" of Marxism that lead to millions of deaths).

Neoreaction is just another form of asshole-ism in the blogosphere.

People have strong reactions to it and thus its proponents should not be surprised when their belief colors other peoples' judgement of them when they want to talk about something unrelated at a conference.
I just mean any kind of CRT terminal emulator
Opening a new shell can take ~5s with oh-my-zsh, it's <1s with prezto. Tab completion is also noticeably slower with oh-my-zsh.
Can someone clarify what would happen in this scenario:

- My app requires React.

- My app also requires FooBarComponent whose dist is just a giant index.js which includes its own copy of React.

- Now I get a bunch of errors because FooBarComponent and MyApp can't share anything between themselves. React really doesn't like it when two copies are running.
Sorry that happened, it's not perfect and sometimes things go wrong. If this was several years ago, things have improved a lot since then.
Don't only think of it as having a speculative value. Think of it also as having the utility of being able to write to an immutable public ledger. Think of "Bitcoin the currency" as a commodity that lets you write to the Bitcoin blockchain like how ink is a commodity that let's you write on paper.

You don't need to use much Bitcoin in order to secure a lot of data with a timestamp and signature. This makes it great for synchronizing all sorts of transactional data across service boundaries meaning people can bring their ownership rights from provider to provider.

With something like keybase.io you're reliant on them to authorize the link between a name and your public key. You're also reliant on the DNS system. All of this adds unnecessary friction to the concept of individual ownership of digital properties like domain names to say nothing of owning the rights to a named module of published open source code.

The speculative value is what drives the mining process. It's a dirty little trick and yes, it encourages a bunch of people near cheap hydro power to buy a bunch of machines that do nothing other than play the SHA-256 lottery.

You can still have zero interest in the speculative value of Bitcoin. That's the miners concerns.

Your concerns can just be the transactional fees that let you embed your own data in the consensus ledger.
Any thought of supporting Django? Deployment is one of the more off-putting things there; looks like this approach could greatly simplify things.
E.g. it harms me a company raises the price of a product that happens to be in demand ("price gouging") but that company has every right to do so as it owns the product.

Actually, 30+ US states have laws making "price gouging" illegal, though the definition isn't just that the product is in demand, but that there is also a state of emergency fueling that demand.
The simple rebuttal to that is that modules that are collections of small functions are easy to reason about as well, and don't the downside of increasing the metadata management to useful function ratio nearly as much. Why have just an average (mean) function, when it makes sense to provide a median and mode as well? Even then, you might find that there's a bunch of extra math operations that are useful, and you might want to include some of those.
Kaldi + voxforge
http://kaldi.sourceforge.net/about.html
http://www.voxforge.org/
Yes, we have.

The entire Javascript ecosystem is a huge catastrophe. It will collapse any time soon. It's complex, fragmented and no one really likes it. There are a dozen different tools to get started. No one even understands how to get started easily. There are no fundamental tools. Everything is changing every week. You can't just build a product and then rebuild it even a month later. Nothing works anymore a month later - your dependencies have changed their APIs, your tools have different flags that do different things, there are new data models that you never needed and shouldn't even care about.

The developers are in high stress. Devops engineers are in even higher stress because they get to see what developers don't.

It's a huge mess and my advice to "prefer core-language solutions to small abstractions to small helper libraries to general libraries to frameworks" (http://bit.ly/1UlQzcH) hasn't been more relevant than today.

Software should be developed using least amount of complexity, dependencies, effort and using fundamental tools that have been and will be here for the next 20 years. Cut those dependencies, you don't need them. They're here today and won't be here tomorrow.
Thanks for the followup. Hopefully this moves on to better places.
No it doesn't. It comes with template strings. Any sprintf type functionality requires you to call functions on the input. It is a tiny tiny step forward.
Yeah look at all these modern languages that do so much for you, like .empty() on an array -- have we forgotten how to do simple comparisons?! You could just take a second to consider the properties of an empty array, namely it contains no items (.count() == 0).

My point being, if something is a completely reusable and basic feature, a dependency is totally just. I remember a few years ago when I and all devs I knew (which weren't many, I was maybe 17) had our own libraries to include in all personal projects we made. It contained features we had to look up once and from then on just automated and imported, stuff like password hashing or input checking. This went out of style as single-programmer programs are going out of style, but the little useful features are still there.
Also, Node.JS modules can be used browser side. On the browser you only want to include code you're using so you're not making the client downloading excessive code. A large 500kb module with one useful function is worse than a one 10kb module with the one function you need.
Google Data Center 360° Tour
Programmers haven't forgotten how to program. JavaScript script-kiddies never knew how to program in the first place.
How to start an online business without money
A friend of mine has his staging databases restored every morning (and anonymised) from the previous day's production backup.
Tangentially related: Does anyone remember the name of this startup/service that was on HN (I believe), that enables you to infer actions from plaintext.

Eg: "Switch on the lights" becomes

{"action": "switch_on",
"thing" : "lights"
}

etc.. I'm trying really hard to remember the name but it escapes me.

Speech recognition and <above service> will go very well together.
FooBarComponent shouldn't have been packaged that way (it can include such a dist file for some people to use, but the npm package shouldn't export that). The typical way is for it to not include React as a `dependency` at all but a `peerDependency`. Then everything will be importing the same instance.
> Are you sure a court wouldn't consider that qualifying as a famous mark? I'm not going to dig into case law, but my guess is it very well could be.

Teenagers represent 9.5% of the US population meaning that 3.8% of the US population (using their 40% figure) have "used" their app. Alternatively the 240 million registered users would imply about 3.5% of the total global population has used it.

I can say that I honestly have ZERO doubt that "kik" would never be ruled famous by any possible measure.
Maybe some people just want to claim they have a published module. Making them feel some sort of achievement or glory.
Well, from the FBI's perspective, they may already know the data on that work phone is worthless, but they just pretended it's not to get the precedent against Apple.

From Cellebrite's perspective, they should've probably asked more like $1.5 million to solve "such a valuable case", as the FBI has made it to be in public (and if this is indeed that contract, which it may not be). Apple also helped there by talking about how much of a burden it would be to unlock it.
That's not true. In most javascript implementations, integers will be represented by real 32 bit integers.
I know people who work in enterprise customer support, on expensive software applications, that are far more complex tickets than just refunds and bug reports. They make good money.

Another guy I knew moved from support into being a "sales engineer", which is basically helping to sell software to the more technically minded, demo it properly, assist with integrations, etc. That's also well-paying.

Bottom-line is, if you come out of college with an English degree and want to work in tech, you need to get your foot in the door somehow, and support is an option.