skysight-inc/HackerNews huggingface dataset:
GE is imploding from what I can tell. Their medical imaging and drug systems are an absolute shambles. Staff are walking out and not coming back. They aren't controlling what's happening, they are in some sort of death spiral as far as I can tell. Australasian former GE customer here.
Sounds most interesting. Do you have examples?
This is a very, very wrong, and unnecessarily harsh and personal in its wrongness, comment. The person you are replying to is dead on and I suspect you are conflating "I support a lot of virt environments in my profession" with the state of the industry.

At scale, in prod, virt is legacy. Aside from Linode where I obviously ran virt, the only virt I've ever touched in private datacenters is relegated to labs or testing farms. We have a lot of tech, both from supercomputing and the new valley stuff which is inexplicably rewriting all of that, that makes virtualization completely unnecessary outside of a multitenant situation with separate paying customers and security domains. Even there multiple vendors are working on it, notably Intel, who is pushing VT-x into containers with multiple efforts.

Don't be so confident to talk about reality, because yours is very different from mine. The original poster was unguarded with their claim but in terms of winds of the industry, they couldn't be more correct, and if you think I'm wrong you're on the wrong side of the shift that is coming, nigh already here.

Example: We bought space in Virginia for Foursquare and didn't deploy a single byte of virt. My current employer has dozens of facilities and virt is a lab thing. No prod, anywhere, across dozens of products and lines and organizations, uses virt. Google doesn't, right you are. Nor does Twitter, who is deep into Mesos (same for everyone who is also deep into Mesos or its many friends).

You might scoff and say well, my CIO says, and you'd be correct today, but the state of the art for resource utilization at scale moved away from virt because we figured out that running full operating systems next to each other as a bandaid for bad CD and provisioning and resource allocation stories is a shitload of overhead for zero gain. There is absolutely nothing that virt gives you, aside from a perf hit and unpredictable low-level behavior (some of us care about cache lines and context switches), which cannot be implemented with tooling atop bare metal platforms. Virt makes your hot aisle hotter so you don't have to figure out bare metal provisioning. You should care about that, then figure it out. It's not hard.

If you are strongly convinced that I'm wrong, much like your neighbor posters, the state of the art simply hasn't made it to you yet. Sorry. You should be willing to consider, however, instead of sniping at change like your tone will keep it at bay. There is a lot of denial in this thread, and it's trivial to deduce why that is.
This is such a horror when shopping in the US. Why bother putting a price tag on things when the price you pay is different. How would a tourist know what the tax is when it changes multiple times over a car journey? It seems archaic.
I don't really have a way to judge the scale. I'd guess the lion's share of the operating costs go to the crew (60!).

Moving that thing's fat ass around probably uses a ton of fuel. I'm sure marine diesel spews out its share of co2, but more than a jet? I thought boats were super efficient relative to air travel.

I guess if your point is, rich guys screwing around shouldn't produce CO2, then, yeah, anything over 0 is bad. That seems unrealistic. any idea how to get a handle on how bad it is? how many cars worth of pollution it makes?
Funny parallel to life in SF and NYC.. My sister bought a 2-bedroom condo in Vail for about 1/5th the price of a similar one on my street in SF. Her income is definitely lower for a similar position, but I'd say the quality of life is pretty good when she can hop a free bus and be skiing in 10 minutes.

She's definitely fortunate to be in the 'professional' class though. Most of the seasonal workers (largely South Americans and college-aged US students), the restaurant / cleaning staff (largely hispanic families), and the otherwise low-income live 20-30 miles away in trailer parks set up by Vail Resorts. They used to live on the other side of the highway, but that land was too valuable so they tore down the worker housing and are constructing luxury condos instead.

It all sounds very familiar.
The first Javascript post I enjoyed reading, this looks simple for humans like me.
It is more readable and more understandable. You should write more Javascript tutorials and show that things don't have to suck. This is how I should have started learning Javascript. I bet the time lost in not using a framework is gained with a better understanding of what is happening and also with an absence of imposed conventions. Just my 2 cents
Thanks for anyone who checks this out. I'd like to release a free API soon with most of the data the portal contains. That's one of my big objectives since hearing about Freebase shutting down. At any rate, all thoughts and feedback are greatly appreciated!
$74 billion convinced me.
Agreed, this blog post is very buzzfeedesque and must have taken an hour or less to bang out... surprised its that high up on the feed.
We know the basic mechanism of action behind SSRIs, but you'd be hard pressed to find anyone that can tell you definitively why they can be effective.

They are some of the most prescribed drugs in America. They have a better safety profile than MAOIs, despite that the latter can be more effective in treating depression / anxiety.
Workstation was heavily developed up until, well, yesterday really.

I personally spent 2 years of my life, starting in 2008, bringing Unity to Workstation on Linux and making it work with every combination of Linux and Windows I could throw at it. That work was continued by a teammate for several years.

I spent 3 years rewriting most of the foundation, UI, and server infrastructure for Workstation 8, bringing the ability to connect to remote VMware ESXi/vSphere servers, along with the server component of Workstation 8. This work allowed VMs to be hosted on any server and accessed from any other server, and allowed VMs to be pushed between servers. 3 solid years on this feature alone, given just how much was needed to make that happen.

In the same release, we replaced the old Teams feature (a single feature that provided a multi-VM UI along with software-defined networking segments) with a series of more independent, more useful features. These were just a couple of the major features released in Workstation 8, and with all this came cleanup in the UI to keep the experience sane, not bloated.

That came out in 2011.

Workstation 9, released in 2012, came with a web-based UI for interacting with VMs called WSX (a feature I dedicated a bit over a year to). It also added UI refinement for the features that come out in Workstation 8, more remote VM support, hardware improvements (USB 3, Hyper-V, OpenGL for Linux VMs, nested/Inception-like VMs), locked down virtual machines for IT, and probably more that I can't remember.

Workstation 10 followed that a year later, and brought guest hardware support for tablets, enhancements for Windows 8 hosts, more remote VM improvements, better command line automation for remote-controlling/creating VMs, and a bunch of other things. UI-wise, it was a smaller release, but it did a lot for the hardware support.

I left around this time to focus on Review Board (https://www.reviewboard.org/) full-time.

Since then, they released 2 major versions: Workstation 11 and 12. From what I can tell, these were largely about hardware improvements and performance improvements, less about major UI changes, but there's a lot that has to happen for these improvements. Hardware improvements are crucial to keeping the VMs useful in many situations. Performance was also a focus. While building these releases, the team was also busy helping out the View team by helping them consume bits of the Workstation/Fusion codebase. They also begun development of AppCatalyst and Flex.

There's also work that happened on Player, Ace, and other things, all throughout.

So that's a lot of killer features in my opinion :) I barely scratched the surface of 8, and didn't go into all the stuff we did in 6 and 7.

We were all very proud of the product, and often spent our free time working on it. I should point out, this was not a large team by any means. It was an amazing team, though. A family. One that will survive these layoffs, one way or another.
If your're not, you're not the target, if your are, you'll feel all the better about it.
This may be due to Intel rather than Apple.
We've been toying with making a page for each day's worth of stories that made the front page that day. For example, you could go to https://news.ycombinator.com/front?day=2016-01-26 and see all the stories that were on the front page at some point today. I wonder if people would find that useful?

We want to do something to help users find the best content they're currently missing. Since HN goes round the clock and none of us does, we're all missing out on something.

(Not quite a direct response to the OP, but it would help with that as well.)
> This is a very, very wrong, and unnecessarily harsh and personal in its wrongness, comment.

In other words, you are ~very~ (edit:) Exceptionally offended that your opinion is different than mine from your experience, whereas most of the paperwork on the industry as a whole does not agree with your experience.

I get that you're mad, but you should take your emotions out of the equation and look at the numbers published by literally every industry analyst.
تور کیش ارزان ورود ۱۰ بهمن ۹۴
Well, it is just slow: bigger the code base / longer it runs, the more clearer this becomes. I used Atom for ~6 months, until I had enough and switched to sublimetext about 4 months ago.
FWIW, I really appreciated this. I think it helped add to the feeling of enormity, and helped me to realize the resolution of the video.
Cloudflare disclose client info on a Twitter discussion
Tall isn't the answer, dense is. The proper question is "when you give up 1km² of farmland, how many beds and offices do you get in return?" (or a little more sophisticated). Tall doesn't actually correlate very well with dense, because it tends to be a small part of the ground.

IIRC Bldgblog wrote that the US has about four ground-level parking spots per car. (Can't find the posting again now, but http://www.bldgblog.com/2007/10/greater-los-angeles/ and everything it links to is a fine place to start.) If you build some highrises, plus big flat malls and office parks, plus four parking spots for each car owner that's expected to move in, plus enough streets, then the highrises don't matter. You could build them half or twice as high and it wouldn't make a real difference to the density.
Sure. Technical Questions are answered and discussed faster on IRC than anywhere else. Nearly all software i regulary work with has active IRC channels as well. (See: Everything Linux to Rails)
First of all that ad was something like 5-6 years after their IPO, so hardly a startup. But anyway their stock price is up ~120% since then.
> Node.js [...] whose idea of having a fun time is throwing promises into the future and hoping that nobody breaks them.

As a non-fan of Javascript as she is wrote I'd hear this criticism and nod in almost any situation, but not while the author is simultaneously advocating writing your stack as a conglomerate of processes written in different languages communicating over UDP.
It's common for something that works well in its original context to turn into something unintended under the pressure of the HN firehose. Sort of a tragedy-of-the-commons variation.
Total rewrites are almost always the wrong move.

It may be true that they meet their stated objectives, but some of those objectives could have been achieved without a rewrite, and some of those objectives don't make sense.

I've written plenty of single executables for multiple targets in Python. Figuring out how to do that would certainly have taken less time than the rewrite.

Small resource usage may make sense, but they didn't relate it to any actual customer need, and given it was already running on RHEL, I doubt this was a reasonable goal. Unless it also needed to run on pocket calculators, the resource needs of a Python program are well within reason for most target environments.

To be clear, I don't think Lua is a worse choice than Python for a new project; my objection is to the rewrite. There are problems with both languages. Sure, now packaging is easier, but when he runs into a hard problem that would have been solved by an existing Python library is he going to rewrite again?

It's a junior developer mistake to blame issues on your tools and rewrite instead of getting things to work in your existing environment. Mature tools like Python (or even to a lesser extent Lua) are rarely the problem.

There are certainly exceptions where there are serious problems such that changing tools makes sense. But none of the problems mentioned in the writeup are that.

The bad part of the rewrite is that there is no possible way to know what was lost. There are edge cases which were discovered and handled in the old product that will have to be rediscovered in the new one.

It sounds like they haven't lost any business over this, so it will be okay in the long run. But I suspect they could have done this a lot easier and cheaper. Just because it turned out okay doesn't mean this is an exemplary choice we should learn from.
No. Your quote does not support your rewording in the slightest. You are interpreting me as angry and offended because it makes dismissing me easier, and because it is mirroring your own feelings, for what it's worth. It's completely irrelevant, but I am not malcontent at all even despite your downvoting me for a well-argued counterpoint.

Perhaps it is not me who should step back and reevaluate.

Part of the problem here is a lack of specificity on the industry. Since you invoked analysts, Gartner and the typical HN view of "industry" are wildly different, but I would posit what happens in what we typically call the "industry" is in the pipeline for the Gartner side in about a decade. However, tickers I would normally put in the Gartner/CIO bucket are aligning with me on this, more than you'd expect. Even Manhattan finance.

And yes, I am aware of CAGR forecasts for virt, but a big driver of the market's growth is expansion of virt deployment footholds thanks in no small part to momentum fueled by opinions like yours. There is also an incentive to sell virt by hardware and procurement vendors, because you need more fleet to do the same work under virt, unconditionally. The market will level off because fewer new projects and companies are reaching for virt as evidenced by, yes, Google, and half the other household names in the valley.

Thought exercise: Google published Dataflow out of their work on streaming architecture and said they are moving on from MapReduce (for the most part). If you got research that says the Hadoop market is growing, wouldn't you look at it objectively in context since the very organization who defined the technology has moved on from it? Market research and analysis often lacks frontline context, much as it does here.
Startup aims to transfer people's consciousness into artificial bodies
New MacBook Air in my hand. It's plugs match my 2011 version exactly, and also match a 2013 MacBook that's here too. Tell her to try again. I find USB fits on the third try.
good to know that XD
My comment was posted before mikeash described his comment that way, so unless you think we should be mind-readers, that's a hindsight fallacy. I never dreamt he was being sarcastic. In fact I still can't read his comment that way—to me it remains a striking expression of the right values of this site.

If I squint, I guess I can see that use of the word "civilized" as a bit aggressive, but really I think Mike was being hyperbolic for effect in his later description.
If you need 0-based arrays, use them. Its no big deal. Any Lua programmer worth their salt knows that Lua uses 1-arrays - so? Set up a 0-array and off you go.
I'm with you that version ranges cause problems, but my belief is that lockfiles are a better solution.

Generally I'd use semver ranges in libraries, and then fixed versions + lockfiles for transitive deps in applications.

I suppose this is roughly equivalent to doing `:pedantic :abort` in leiningen, except you wont't have as many warning to squash - either way you have to rely on the test suite to tell you if the versions you've pegged work.
Yes and no.

Homerolled solutions such as this are free of another developers assumptions, but tend to scale poorly. Generally they need to be modified as new requirements are created, or unforeseen circumstances arise.

Over time you end up putting together more and more logic in and the illogical conclusion is that you end up building your own heavily bespoke version of React/Angular/jQuery/whatever, before realising you actually need to go back and start again.

There is absolutely nothing wrong with writing your own libs (it's educational and character building!) but to chuck json through a constructor is trivial. Sure - this code renders views in a simple and relatively inefficient way, but drawing boxes is only part of what React is doing.
1) How does a GPL'ed reference implementation prevent digital cameras from using the format?

2) The reference implementation will most likely change to a more permissive license, cf https://github.com/FLIF-hub/FLIF/issues/192

3) If digital cameras would use FLIF, they would probably need to implement a simplified encoder in hardware, e.g. one that uses a hardcoded (set of) MANIAC tree(s) and only uses a subset of the available encoding options. Otherwise it will be too slow.
This is the type of article that spawns the best and most informative comments. As a rather isolated programmer being able to browse through the HN comment section and read everyone's different perspective of "rules for becoming a better programmer", I find is infinitely more constructive than reading blog posts. It also somehow feels more credible... So thanks I suppose.
It basically is. It's almost exactly verbatim a statement made by Google when talking up their container game.
Interestingly, the drawing tools in MS Office traditionally use VML, which is an XML format MS submitted for standardisation. The W3C decided to add their own creative touches to VML and it became SVG.
I must agree. Starting with jQuery is becoming more and more common, you get immediate results but don't know WHY and HOW it involves Javascript. Breaking it down into pure JS like this is great.
Okay I think the author is severely misinformed as to why we use React. I say this because the very first thing he says is to use MVC architecture and then goes on to write his own framework (from scratch???????)

...Why?

This solves none of the problems React was designed to solve and only makes things more complicated by introducing new APIs only you know.

Yes, this approach with vanilla JS is great for small apps. What makes you think this app won't grow?

I hardly see how this is a reaction to React other than to say "I didn't really read into why people are using React or what it's trying to solve, but I'm pretty sure I can solve this problem with my own framework I just whipped up.

Sorry for the brash delivery.
Debuging Push notifications with Knuff
#Aston_Martin_Vulcan #Up_For_Sale at $3.4M
I wonder if there's a business in offering to fly a swarm of large drones in the Fresnel zone of the customer's choice.
Hacker News Telegram channel
Paul is a ship owner not a captain.
Life of a French Model and Skateboarder Living the LA LifeGo Follow Him
I totally agree with you on the scalability aspect, but I think one of the main issues correctly pointed out by @ilovefood is that a lot of juniors nowadays start directly with one of the big frameworks, with no idea on what vanilla JS is.

I really hoped that we learned something from the jQuery experience but it seems to happen again and, maybe this is just my feeling, but JavaScript is kind of the only big enough language with this issue.
Either I live in a world where a startup is being stupid and flagrantly spending millions on an ad during superbowl, or they'll be a raging success....by spending millions airing ads which appear to insult their potential customers and pandering to base exclusivism...

Its like a social desirability Catch 22...either way, we lose.
I think I disagree with this, but I'm not completely sure.

If everything is going to micro-services, don't we want to move staging from a monolith to staging the services? Than we test against a staged service and push to production.

With so many moving parts, it seems to me going straight from QA to production could still lead to problems.
> he earned every dollar

bullshit. People get rich on the unpaid labor of others. If nothing else, he would have less money if microsoft didn't participate in the anti-poaching scandal. It's clearly not his fault, but he got money because his corporation didn't pay market wages.

edit

This is, perhaps, a little harsh. I don't think he's a villain. I've never met the man, but i'm sure he's a decent guy. But you have to admit, his net worth is not a perfect reckoning of the value he created in the world. He's rich. good for him. Some of that money came from him, as an owner, colluding to not pay fair wages. This is just the most recent example. There was the whole temp workers thing. Microsoft has a fairly shady history.
> Developers who deliver 10x as many features inherently do so at the cost of maintainability

I don't think what you say is completely true. People who are more experienced tend to be able to produce features much more quickly than those who are junior, just because they've already run into issues before so can anticipate them or solve them more quickly. If anything I would argue people like that actually write code more quickly that is more maintainable.

I don't know if he can ship 10x as many features; I didn't think term 10x engineer was used literally. I just know I've worked with quite a number of people and he is one of the best developers I know.
Skicka – A CLI for Google Drive
> That's not true in the slightest, drunken driving laws don't measure the drivers impairment but BAC.

They measure the impairment and BAC is an instrument to that. Otherwise it would be of no interest. There used to be other impairment tests, like walking the line, before breath testers became commonplace.

> And in any case, attempt implies intent.

As manslaughter is an unintentional killing, I thought the metaphor was fairly obvious.

You know drunk drivers are prone to committing manslaughter other variables being equal, you do it anyway: well that's an attempt. Rationale behind it is irrelevant, just like noone cares you needed those money badly when you killed that cashier.
Yeah, this is weird, my son loves games, and he would be frustrated quick with no instructions or hovers on action buttons. No idea what the point of this game is, what the rules are, how to score points, why somthing is right or wrong. You need to improve the experience here.
> It could be a compelling story, except IBM has already talked about how datacenter sales have dropped, so the US at least is probably overcapacity at this point.

Counterpoint: Dell's modular datacenter solution is doing well and really murdering the competition.