skysight-inc/HackerNews huggingface dataset:
If you don't care about the stupid arbitrary bundling system for other assets (like CSS and images) that WebPack has (and you shouldn't: it's an awful code practice) then yes... Browserify is literally better in every way (other than tree shaking)
Well, that was a charming response.
This makes us at WooCommerce very happy!
We discussed this on Twitter Dan, fyi, no need to rehash here.

But they very fact you had to spend time abstracting away WebPack speaks volumes IMO...
They quote Mr. Musk in the article, but it seems Toyota and Honda feel differently.
I don't think it should be stated as universal. Some blockchains can have immutability as their absolute raison d'être, others may have it as an important goal, but may sacrifice a certain degree of immutability for other features.

Whatever is going to happen, monoculture won't be the solution.
I know there's a startup mentioned in eetimes working on daimond chips. It's startingin power chips, but i think they talked about going full on semi.
> Code vs config is a huge bikeshed

Not really. Historically it's been an indication of the quality of a system.
You've got "data" and "experience". I also like the part of your post where you are implying that using dynamically typed languages is some sort of act of defiance. What typed languages have you used?

Btw do you care about John Carmack's opinion on the subject?
AudioContext is a special case – unlike most of the THREE.* exports, THREE.AudioContext is a getter (which initializes a Web Audio context). ES module namespaces can't have getters, so for backwards compatibility in the generated UMD bundle it was necessary to add that snippet to the bottom.
OwnCloud/NextCloud
Yes, but that's not saying much is it?
If you find yourself agreeing with this: https://vimeo.com/14629850

Git is powerful and amazing, but not simple.
If the loss had happened to anyone else other than the people behind Etherium, the fork would never have happened.

A fundamental problem with Etherium is contracts between anonymous parties. If the other party in the DAO hack was discoverable, the hack would not have been a major problem.

Executable, rather than declarative contracts, are probably a bad idea. Putting in a virtual machine is a cop-out - it means you don't know how to solve the problem of expressing contracts formally, and are pushing it off on someone else. That someone else will probably botch it, as the DAO did. I've previously suggested that decision tables [1] would be a better basis for a contract system. This decision table tutorial [2] is something of an ad for a tool, but it uses as an example the sort of things one would want in a contract.

[1] https://en.wikipedia.org/wiki/Decision_table
[2] http://reqtest.com/requirements-blog/a-guide-to-using-decisi...
But there will be problems with those serving the web pages being served a notice as they do today whenever someone torrents without a VPN. It isn't inherently anonymity focussed like tor.
I think you outlined a bigger issue: It is now clear that the community will ultimately decide what is right, and the 'community' is actually a much smaller subset of people using ethereum then you would hope. The original idea was that ethereum is 100% immutable to anybody - that no entity can go back and modify it. But as we see here, that's not true, because through a hard fork (that they are clearly willing to do) they can force things to change.

The issue is that ethereum isn't the only option here - standard legal contracts exist, and are by far more common. The only real advantage ethereum offers is the immutability aspect - that no one can go back and argue the contract is wrong or invalid. But now, without carrying an immutability guarantee (Or you could say, now that it is clear that it never had such a guarantee), is there really much of an advantage to holding your contracts at the whim of the few controlling ethereum vs. the legal system?

If the miners lose a bunch of money due to X, and your contract happens to also be based on X, what do you expect to happen? I can't imagine that it is out of the realm of possibility for such a situation to happen.
It was clear to me that you weren't making an endorsement.
Where does considerable cost come from?
There is a small overhead in number of characters in your program. I think that's it.
PYTHON PROGRAMMING FOR HACKERS.PT 4 – DICTIONARIES CONCEPT
Do you know if there is anyone working on declarative contracts? I was thinking that at least some sort of declarative way of bounding the contract's behavior might be useful.
> I also fundamentally disagree that plugin repos are a good idea

Part of the reason I was motivated to do this work is that I love Three's batteries-included approach – I don't need to spend a long time configuring my project or trying to figure out how to glue different libraries together (I've written more about this here https://medium.com/@Rich_Harris/small-modules-it-s-not-quite...). Nothing has changed vis-a-vis Three being a drop-in file.

But it's a double-edged sword – batteries-included historically means including code that you're not using in your project. ES modules give us the best of both worlds via tree-shaking. And once you've learned them (you're not learning Rollup, you're learning JavaScript – this is a standard we're talking about) you'll find it's much more logical than the alternative. Trust me!

The KeyframeTrack thing is just a special case resulting from the codebase's history. It could easily be fixed more elegantly, it was just outside the scope of this PR.
> Magento, one of the largest open source e-commerce platforms, ships a broken cryptography library that clueless developers are probably using to encrypt your credit card information for their client's customers.

Nope. There is a built in credit card method that would utilise the Magento crypt() but you cannot actually hook this up to a bank and get any actual money. The lamest of lamest Magento developers will use an off the shelf payment gateway that will use things like iframes so that even a non https Magento site will not have any credit card information pass through Magento, instead you get payment references.

In theory you could break the crypto and get into Magento admin, to then export out customer email and address details. You could probably refund all customers orders but not get fresh money out of them.

I appreciate the code may be 2008 vintage but there is no new vulnerability here that gives any means to access any Magento credit card data in a meaningful way, e.g. a lucrative way.
You just argued that OpenBSD is more secure because it has specific feature set. You didnt prove these are the right combo of features, that they in solo/combo work against strong attackers (instead of obscurity advantage), or even strongest ones of their respective classes (they're not). You started with OpenBSD's features, accepted the claims as fact, ignored all other tech/requirements, and then asked other party to prove their claim with evidence.

Wrong way to do an argument for or even against OpenBSD. You need to establish requirements for security in many areas, features/practices to support those, assurance they work, and then what each OS or system possesses. OpenBSD has only partly done this so I doubt uou have. I look forward to you posting that analysis for OpenBSD and its preferred hardware.
On a slightly related note, has anyone tried Thync (http://www.thync.com/). It uses tDCS. Wanted to know anyone's experience with the device?
The whole AWS APIs are formalized and exposed in different ways and that formalism is one of it's strengths: everybody can write a transformation that creates a bindings for his language of choice. For example of this take a look at:

https://github.com/boto/boto3/tree/develop/boto3/data

P.S. Agree that not all of the services adhere to the same bar.
I would find it interesting to know why refactoring tools are successful in Smalltalk but not JS.
I'm not surprised that the non-programmer segment of ETH supports the hard fork, but (imo) it should be very easy for those familiar with software development to see why it has to be absolute 100% or rather completely useless. Specifically, it's about turning real world requirements into code.

Most of the legal contracts dispute isn't about blatant black and white issue, it's about whether this interpretation or that interpretation of the same wording is the intentional one. And it's obvious that we have enough issues with just turning requirements for CRUD websites into code, there is zero chance in hell there won't be "requirement bugs" in more complicated contracts. Unless you agree with the 100% "code === law", you will get every dispute from the old legal system, plus a whole new class of dispute from those aforementioned bugs.

It does raise the question of whether all intentions of legal contract could be turned into code at all. But if that's a no then ETH is dead even before it's started.

In other words, our legal system is already 99.9999% good, it's the last remaining 0.0001% that ETH seems to try to replace. And now it seems like it doesn't want to?
Couldn't anything metal be a rust hazard? Am I allowed to own a metal mail box or is that a rust hazard.
Welcome to reality. Follow all responses that say to focus on customers (either users or revenue). Flash in the pan hype are blips on the radar for the marathon you are just now starting
Platfora is acquired by Workday
2 months
Here we go again.

As we've discussed before, there are problems that are inherent to designing distributed systems that are not solved by SmartOS's magic sauce. Please stop pretending that every possible problem that is faced by GNU/Linux technologies has already been solved by SmartOS, it's getting quite tiresome.

"Storage with containers" refers to correctly decoupling the state from your application and storing it a way that allows for horizontal scaling. It's not as simple as proclaiming "we have a magical filesystem, therefore all problems are solved and you should use SmartOS kthxbai". There are harder problems here, and no amount of SmartOS shilling will get around that.
Have they solved the problem of where hydrogen comes from? Last time I looked this up, the main process for making hydrogen is the shift reaction, which is hardly carbon neutral.
[MUST SEE] Beautiful Girl Translates Emotion of the Song into Movement
All journalism is pretty bad. Non-experts are producing content under severe time constraints. Most newspapers barely have a budget for copy editing, let alone fact checking. Take journalism for what it is - disposable content written in a hurry.

http://www.goodreads.com/quotes/65213-briefly-stated-the-gel...
As we all know abstinence-only doesn't work, so maybe there are stronger parallels here than at first glance. ;)
> This means that there is a conflict between performance and having a well structured object oriented framework.

What do you need a 'well structured object oriented framework' for? You're going to build up a huge object graph in memory, to output some HTML, and then throw away all the objects at the end of the request. Nobody is going to see your beautiful object tree, so don't bother. A blog entry page should be super simple.

header, title, content, comments, recent comments, footer.

Header and footer are dead simple echos of the boilerplate, maybe replace in the html title or something. Read the title and content from disk[1]. Have another data file for all your articles for the index page.

I prefer not to have comments on my blog, but if you must, you can put them in a database; limit to something like 100 or 1000 comments per article (because really) and limit threading, and it's going to be pretty quick to query them (make sure your webserver is doing reads from a database in the same metro area, if not on the same box).

Recent comments is across all blog entries; I would probably add a index on the time in the comments table and just select 2 from there; you could union that into the earlier comments query if you don't want to make two round trips to the database.

You don't need to do this with concurrency, each page load has barely anything to wait for, so more threads doesn't help throughput. Run enough php workers (php-fpm, or apache children if you're using apache_mod_php) to keep your cpu busy, and you're golden.

[1] There's four articles on this blog -- it doesn't need a database. PS run php as a user that can't write anywhere on the disk, and push the blog entries and the summary datafile with another user.

Edit to add: If you skip comments (or outsource to disqus or some other comments w/ javascript platform), you can make the whole site just static html, and leave PHP at home. OTOH, these guys are running Wordpress, because they like frequent security updates?
I don't understand why you were downvoted. I think you bring up very valid points about the state of education that is required for wide spread adoption.
> I think Ethereum has some good leadership, but I think this is something that they really need to get a policy on now.

Do they? I see a brilliant 22-year old in Buterin, some respectable people like Gavin Wood and a massive crowd around them that has perverse incentives. An organization that has a massive amount of money (and people who want to make money) and with that the desire to reinvent everything (think I'm kidding, go read about dapps).

Hang around a cryptocurrency forum for awhile an you get an idea of how delusional and downright scammy the vast majority of those communities are. 18 year olds from Sweden scamming people and running pump and dump schemes and then getting doxed and threatened and people investing their life savings into stupid altcoins (yes, saw both of those, as well as much more). It's like the payday loan industry, and like that industry the people at the top have no reason to clean it up. Not only are they not cleaning it up, they are encouraging it. In the r/ethereum subreddit in the early days Youtube videos comparing Buterin and Jobs were getting voted up without even a second consideration that it might be premature.

It's easy to rant against the evil of the banks and the people in power when you don't have power, but when you have power, you do the same?

Something is wrong with Ethereum and scams like this have a chance of destroying cryptocurrency from a legal standpoint before it even gets started.
> until you start generating lots of garbage

We should really stop pretending that the garbage collector is the problem with langauges. The collector isn't the problem, your garbage is the problem.

[Not that I'm a proponent of PHP, though it does make popping shells far more fun.]
Nike Chalkbot was a project by Pittsburgh-based Deeplocal: http://www.deeplocal.com/projects/chalkbot.html
The concept of a long tail of less frequently useful features is intrinsic to software tooling. It's tempting to feel bad about only using the handful of primary git commands (status, add, commit, merge, branch, push, pull, log), but the reality is success in software development means applying exactly this mentality to most tools or technologies you encounter.

Figuring out exactly what you need to know to satisfactorily handle most situations (and then Googling the rest of the time) is just a smart way to be a developer.
Sources: Cyanogen Inc. is undergoing major layoffs, may "pivot" to apps
A titanic system.
Has this been edited since it was originally posted? I recall reading something about setting money on fire in the one version back in the day...
IPFS works over tor! The implementation is pretty rudimentary at this point, though.

I guess the main issue is actually distributing the tracker.
I've had a similar experience in big companies. While you're learning and you're challenged technically, all is good. Once you master most of it and start asking the deep questions about how exactly you're helping the world (and sometimes more importantly, the means for that), that's when trouble starts.

E.g. "kicking ass" improving infrastructure performance and having fun, then your boss asks you to delay (or never implement) certain improvements because it will be hard to justify the body shop headcount next month.
Really good write up. Some people are really smart, I wouldn't ever be able to do that kind of stuff even after being programming for years.
#DNCLeaks disappears from trending news as WikiLeaks emails released
That's A bit of an exaggeration. My wife is a mental health professional in Japan. She tells me that about half the people in the general population she speaks to find the topic challenging. Others are fine. Her hospital is not at all hidden away.
thanks, this is really neat. i was thinking of something like this and my only idea was to write my own from scratch. while that might be educational it was daunting and i was guessing would have limited support and bugs.
I don't think his opinion matters more than anyone else's opinion. What's more, he's not an especially active member of the community these days.
Here's some third-party implementations of some AWS APIs, with no endorsement of quality:

S3

[A1] https://github.com/jubos/fake-s3

[A2] https://github.com/scality/s3

[A3] http://s3ninja.net/

[A4] https://github.com/basho/riak_cs

[A5] https://www.npmjs.com/package/s3rver

[A6] http://ceph.com/ceph-storage/object-storage/

----

SQS / SNS

[B1] https://github.com/iain/fake_sqs

[B2] https://github.com/yourkarma/fake_sns

[B3] https://github.com/adamw/elasticmq

[B4] https://github.com/p4tin/goaws

[B5] http://stratosphere.codeplex.com/

[B6] https://github.com/unbounce/yopa

----

DynamoDB

[C1] https://github.com/mhart/dynalite

[C2] https://github.com/ananthakumaran/fake_dynamo

----

SimpleDB

[D1] https://github.com/stephenh/fakesdb
You've built a custom system with the exact same business requirements that connect to the exact same different sub systems, api, etc?

Similar enough that I can make good estimates. You can too, with experience.
Anders Hejlsberg is who you're thinking of.

> He was the original author of Turbo Pascal and the chief architect of Delphi... the lead architect of C# and core developer on TypeScript.

(from wikipedia)
This is a death kneel to Etherium. Immutability is literally the only thing that made it stand out from any other form of currency. Now it's no better or worse than any other form of currency. Someone can decide they don't like it and reverse a contract? Done.
i've gone through the very basics of burp suite before but never effectively used it to test much.

so, i did a tutorial search for myself, and if anyone may benefit here's a text one with screenshots: https://www.pentestgeek.com/web-applications/burp-suite-tuto...

and some official video tutorials: https://portswigger.net/burp/tutorials/
Gary Johnson's plan to save the internet
Essentially agreeing with what you're saying, but it's important to note that there are ethics boards and regulations on medical research to prevent situations such as the data obtained by scientists during the holocaust.

A key word is informed consent. Research by its nature is conservative and small steps.

There's a whole world of bioethics out there & it's a common undergraduate major, to continue this discussion :)
> You didnt prove these are the right combo of features, that they in solo/combo work against strong attackers (instead of obscurity advantage), or even strongest ones of their respective classes (they're not)

Security mitigations work best in combinations, the entire purpose is to make it as hard as possible to attack the system.. suggesting OpenBSD's mitigations aren't the strongest in their class clearly needs some proof on your part, but I don't expect you'll deliver.

> You started with OpenBSD's features, accepted the claims as fact.

I stated the facts, because I'm aware of and closely followed their development, having tested them. I accepted no claims as "facts". You can easily verify everything I've said, OpenBSD is open source.. and shocking, they pioneered that too.. having created anoncvs.

Not much left to reply to in your post, because you're just grasping at proverbial straws.
Not an ad-lover or marketer here, but even in the pre-internet days, ads were how you found out about things you might be interested in buying, an information source, sure, to be taken with a grain of salt. But still I bet if you really trace a purchase, even if a friend told you, he most likely saw an ad or a product-based article for selling.

In some cases the ads have been put into the articles themselves, like all of the wooing over the latest Apple products release every 6 months or so. It is driven by the techno-lust for the product. It seems to be, since I have many colleagues who own two or more systems, not including phones and tablets, when one would do. Just look at some sigs in game or tech developer forums where people list their arsenal.
> If the miners lose a bunch of money due to X, and your contract happens to also be based on X, what do you expect to happen?

If the rest of the community doesn't agree, then they will take they economic power away from the miners, change to a different mining/staking strategy, and leave the miners to mine an abandoned fork with a greatly decreased market cap.
Uber Partners with SMSGH to Offer Cashless Payments in Accra
This was explained to me by someone who knows the handset OS integration business: Margins are low and handset makers know they can get Android put on a handset cheaply, by people who specialize in doing it quickly and cheaply. There is no room for a premium player like Cyanogen to provide an improved Android. I suppose many of the Cyanogen people will get scooped up by Google.
Head First Design Patterns is awesome. I read a couple other Design Pattern books, but didn't really get it. I didn't want to buy a "Head First" book because it looked kind of silly, but this book has finally opened my eyes to what Design Patterns are about.
"The all had good features, but..."

I sympathize with the author. I find that all of the alternatives are unsatisfactory.

I made my own solution that handles HTTPS and, most importantly, gzip compression. It's 22 lines of portable shell script including comments. It uses only two small programs: socat and netsed. The limitation is I only use it to proxy one domain at a time.

I tried to offer it to HN readers via "Ask HN" but for some reason the mods quickly banned the account.
So "demand side" means industrial efficiencies? I always thought of it as, you know, less end-usage.

Yes it's a small share of the total, and no I don't believe it's a matter of policy. It's cultural. Whose job do we think it is to "spend within our means" energy-wise? Everyone's? Or is it industry's job to just "make it work" so that we can keep black-boxing power, as we do water.

Example: I was at an airport café this morning and I noticed that the menu was displayed on three big display monitors. They were probably 42-inch screens, all showing the same static image. There were like 6 menu items, all minor variants on a cup of coffee. They were all clearly visible from every possible angle. The same job could have been done undistinguishably well by any single one of them—not to speak of a printed board.

I know, it's an airport for crying out loud. The energy used by those screens is too small to measure. What concerns me is that we (Americans at least) live in a society where someone—I would say thinks this is okay, but really just doesn't think about it at all.

So I completely agree about where our priorities should be, but I think that those levers would be easier to pull if we as a culture had a little more "mechanical sympathy."[0]

[0] http://www.se-radio.net/2014/02/episode-201-martin-thompson-... (Where I first heard of it, anyway.)
Windows 7 Ultimate Highly Compressed ISO 10MB Crack Free