skysight-inc/HackerNews huggingface dataset:
There is a strain of thinking evident in the article, and one I think is pervasive in corporate America today, which is that measurable savings are highlighted while difficult to quantify lost benefits are deemphasized.

When you can't precisely measure how much is lost by doing something half-assed, it's probably worthwhile to do it right.
It will be hard to land a job in US. For Indian national, there are mostly two ways you can do. One is by H1b which is the common route but the company needs to sponsor you for that. If a US company can n't find any talent in US and you apply and convince them that you will bring tremendous value then they will sponsor you. The other route is to work for a MNC in India and get an intracompany transfer(L1).
Since original the file is saved, there's nothing preventing you from closing the file. "Managing to" is as easy as closing the window with cmd-w or hitting the red dot. Previously you could say 'no' to the 'save changes' dialog that popped up reliably - now it's just gone and there's essentially no indication that you can fix it.
Or how about this one: you're editing an existing document and you wish to preserve the original by using "Save As" to create a duplicate when you finish editing, except at some point you hit "Command S" by accident or by reflex and you've now clobbered your original, without warning, and there's no previous version to restore.

That one's been around for 28 years, and was finally fixed in Lion and Mountain Lion.

The "Save As" command has always been dangerous and ridiculous in the way it's typically used for editing and then saving duplicates. Lion finally gives you better and more safer options, but if you're not willing to learn what those are and how it works, if you're hell bent on continuting to do it the old way, then you're not going to like it and you're going to continue to risk data loss like you have for the last 30 years.

I, for one, love the way it works. Yes, I had to sligtly change my workflow but it's change absolutely for the better.
But it doesn't make enough of a distinction in the metadata to allow you to revert. Ideally the process would be "Duplicate -> Revert Original".
Web browsers on tiny devices that have the processing power to do a scaled zoom in a reasonable period of time have most certainly not been around for 20 years.
I see it as part of the iOSification of OS X, to appeal to iPad/iPhone halo converts. My phone has never asked me if I want to "Save changes".
I sincerely cannot remember the last time I had to use 'rpm'. I can't imagine Debian is any different.
Also, with their next "flagship" title, Dota 2, it seems like they're going the free-to-play route anyway, so people who are willing to play for the game itself is going to be irrelevant.
The generic answer must of course be: It depends on your architecture.

My answer assumed that we were talking about replication lag, where you are copying data among the back-end data stores "immediately", which is to say "quickly, hopefully on the order of milliseconds but you can't count on that". Unfortunately, depending on the design of your database, replication is often not "immediate" enough to guarantee consistent results to one user even under the best conditions, let alone when the replication slows down or breaks, and that's why you might build something like the affinity system I just outlined.

The actual mechanism of replication depends on the data store. MySQL replication involves having a background daemon stream the binary log of database writes to another daemon on a slave server which replays the changes in order. (Of course, multiple clients can write to MySQL at a time, and ordering all those writes into a consistent serial stream is MySQL's job.) Other replication schemes involve having the client contact multiple servers and write directly to each one, aborting with an error if a critical number of those writes are not acknowledged as complete - and then there presumably needs to be some kind of janitorial process that cleans up any inconsistencies afterward. (I'm no CS genius; consult your local NoSQL guru for more information. Needless to say, you should strive to buy this stuff wrapped up in a box rather than build it yourself.)

As for "shards", that's different. My understanding of the notion of a "shard", as distinct from a "mirror" or a "slave", is that it's a mechanism for partitioning writes. If you've built a system with N servers but every write has to happen on each one, the throughput will be no higher than on a system with one server and one write, and you're doing "sharding" wrong. What you wanted was mirroring, and hopefully you weren't expecting that to help scale your write traffic.

If data does need to be spread around from shard to shard, hopefully it has to happen eventually rather than quickly, and some temporary inconsistencies from shard to shard are not a big problem. So you can use something like a queueing system: If you have some piece of data that needs to be mailed to N databases, you put it on the queue, and later a worker comes along and takes it off the queue and tries to write it to all N databases, and when it fails with one or two of the databases it puts the task back on the queue to try again later. (Or, perhaps, you put N messages on the queue, one per database, and run one worker for each database.) You'll also need a procedure or tool to deal with stale tasks, and overflowing queues, and the occasional permanent removal of databases from the system.

This soliloquy is looking long enough, now, so it seems like a good time to reiterate patio11's point: Don't build more scaling than you need right now. Hire someone to convince you not to design and build these things.
In this case, the downside to saving money by laying off expensive experience is clear.

Things like time developers spend doing traditional IT tasks are clear to developers. But it's amazing how little of that is visible to executives. They certainly don't get an hour-by-hour breakdown of where developers spend their time. And the time to develop software is notoriously difficult to estimate even using the best techniques out there -- and most people just eyeball it. So executives really can't quantify the loss of productivity, they just hear programmers bitching.
I'm sure you also believe the UX in any given video game should be patentable, and video games need to license each other for the effect of tapping buttons here or yanking joysticks there in order to even build their own.
very nice article. given its likely target audience, though, he really needs to explain explicitly why mark-and-sweep can't compact as it goes, rather than leaving a fragmented heap.
Maybe we should ask Mr. Java, if he has other videos about multi-touch!!
> So now every program needs an infinite, crash and restart resistant, fine grained revert option.

Yeah, which is why Apple added that in Lion so anything using NSDocument get it for free http://support.apple.com/kb/HT4753
Anyone coming from the iPad has no experience with the File menu, and Mac users have years of experience with it. Learning a new interface requires learning some new customs.

This is a huge issue with creation in iOS. It is not a form factor or input problem. It is this strange assumption the every action I do is correct and needs to be preserved. I cannot know that my rewrites will be good before I attempt them. Reverting on iOS is a huge pain if its even possible at all.
Techcrunch. Next question.
Kudos for this man to stand in front of an audience for 3 hours without pauses.

I'd not like being there, give me a break, put different people on stage, add more visual aids. Too tough to hear, even when I could stop the video and I'm very interested in what he says.

He is right about Linux, Linux is not there and who knows when it will. If tomorrow is, Carmack will support the platform fast. He follows the market.
I honestly don't see why people are so upset. I think the way saving is implemented in MLion is fantastic. Instead of relying on old standards, the engineers are looking ahead of the time.

"Normal", non-tech people who aren't obsessed with technology, will find this feature amazing. Actually, let me correct myself - they won't notice this feature, and that's the key.

Save As was a hack, which worked for people who knew about it, but was a total clusterflack for normal users. Normal users rarely revert to old copies and if you really want a duplicate of a file, well, you can always have a "duplicate", which is an available feature.

Using the OSX in this way will be a more pleasant experience, going forward. I am not saying this because I love Apple's design, I am saying this because I've seen this countless times while helping my family with their computer issues.
A little off-topic, but I was there at that speech. Notice the length of that video... the man can talk.
I like the feature, to be clear. I just think it's horribly executed, and the education side has been even worse.

The problem is that they took something. Then they changed it, giving it multiple nearly-invisible modes it can be in, which changes from application to application (not all have a 'revert' option, even for versioned files). Then they didn't tell anyone.

For instance. I just cropped this file. How do I know the original still exists? http://cl.ly/image/2L2X0x042W0N

Here, I opened it in another application. Are there multiple versions? http://cl.ly/image/3Y1m3C2r1r2f

What about in the File menu? http://cl.ly/image/0F2o2H2i3Z2f

Finder? http://cl.ly/image/1C0S3z3Z0q30 or http://cl.ly/image/463p0O1I3q1C or http://cl.ly/image/1F191E3b3U1W ?

(edit) Oh, cool - there's a "Versions" column. Maybe that has it: http://cl.ly/image/2703273U3z2U

This is bad.
Once again another cautionary tale about why you should be paranoid about the security of your devices and accounts.

When securing anything, the best philosophy is to just assume you're going to get hacked and act accordingly. Linking accounts, weak passwords, and no encryption? You're just putting a target on yourself.

Best advice? Keepass, Whole disk encryption and using anonymous information is a good start. Keep your stuff and accounts in separate silos, and stay in the shadows.
These facts stand out about the Olympics:

- Phelps has won more Olympic medals in his career than India in all Olympics

- Jamaica won 2 medals at women's 100m a few minutes go. Bolt still has to go. Why Jamaica?

- The United States has heavily relied on its dominance in swimming, racking up 23 of its 37 medals in the pool.

- Kazakhstan has 5 medals, all gold! Four in weightlifting. Population is barely 16 million

Will be interested to find more
Look at it the other way: With the old system, if you pressed "Don't save" to that dialog by mistake, you lost everything. With the new system, it's basically impossible to lose anything (the only way is if you don't notice for long enough that the old version gets reaped).
Apple's Case Against Samsung in Three Pictures
The title is a bit misleading. What crash does it discuss?
Yeah, after reading your post twice and confirming with cat in the terminal it sort-of makes sense.

They still shouldn't list "Save as..." as a new feature, because it sounds like they made it work like every other OS.

Also, the textedit window is extremely deceiving when it shows "file1.txt - edited" -- when in fact the file has already been committed to the filesystem!!
Lisp machines belong to a past so distant I don't think their are relevant for exploring the possibilities of contemporary hardware. The design constraints moved - clock is in the gigahertz range, memory is orders of magnitude slower and we have to deal with multiple levels of cache between them. And that's just the start.

In fact, the concept of "doing it in hardware" (be it specialized logic or dedicated generic processors) is alive and well (and bearing fruit) on every mainframe manufactured.

The fact we all use similar x86 boxes designed to be compatible with MS-DOS is a tragedy.
apt-* and yum are only minorly better than rpm and dpkg, and are still ridiculously over-complicated. The proliferation of extra tools to deal with package management are a testament to the number of people that are unhappy with the current options.
I disagree, the US just isn't that different. Yes, theres small pockets of intense difference, often composed of first and second generation immigrants, but otherwise "American" culture is fairly homogeneous thanks to mass media.
5Degrees' serial recap of The Lean Startup (plus some cool infographics) 6/10
I am trying to resist the urge to call Mountain Lion "Mountain 'O crap"

If Microsoft did this they'd be eviscerated crucified.

iOS Developer and Mac user here (as well as Windows).

The madness must stop. I have a feeling Steve will be missed more and more as the years pass.
There is something similar in Breaking Bad.
The OP does have details to back it up, just not hard numbers. He states how new employees had problems getting setup, old employees dealing with misc problems, things not running smoothly in general. Yes most companies consist of more than IT but these days the problem is many organizations seem to look at IT as an extra expense they can skimp on or even completely do without("The bosses son is really good with computer's he can fix any problems that arise!"). Theres two sides to every story and maybe this department was bloated and could've used some restructuring we don't know that part for sure but we do know that things went from everyone being able to work efficiently to all sorts of random issues, suffered by general employees not IT that should've been avoided.

You're taking this awfully personally, I'll ask again do you do in some sort of managerial position? Do you have some personal experience with this sort of thing?
I completely agree. A split second of poor judgement can destroy hours of work. In this case I'm happy to let Apple save me from myself.
I tried that, but then my backups got eaten by a high horse, high on horse.
Well, it seems it's been made even more dangerous. Why not remove it, re-label it?
I guess I really don't feel you. 'yum localinstall' is absurdly simple as far as I am concerned, and the standard 'yum install' is obviously even simpler. I am not even aware of any additional arguments localinstall takes. If there are any, I have never used them.

Edit: I just checked the manpage, and it seems 'localinstall' is deprecated. Simply using 'install' now does what it used to, though 'localinstall' still works for backwards compatibility. It really could not become any simpler.

Complaining that 'rpm' is complicated is like using git without the porcelain then complaining that it is complicated.
Double tap to Zoom patent? Lol, that sounds completely pathetic. I thought about that by myself in a couple of days after starting to browse the web with a mobile that wasn't from apple. Now i understand why it's so easy to create virtual monopolies. You don't have to be particularly smart, just the first average joe to come up with a simple idea, then just stifle natural progress with dumb laws to make some guys rich.
In not a too distant future, people will look back at this society and be genuinely mesmerized at how retarded people were.
"We shall repeat here without apology--for the warning cannot be given too often--that the investor cannot hope for better than average results by buying new offerings, or 'hot' issues of any sort, meaning thereby those recommended for a quick profit. The contrary is almost certain to be true in the long run. The defensive investor must confine himself to the shares of important companies with a long record of profitable operations and in strong financial condition. (Any security analyst worth his salt could make up such a list.) Aggressive investors may buy other types of common stocks, but they should be on a definitely attractive basis as established by intelligent analysis." - p28 The Intelligent Investor (Revised Edition 2003)

The IPO market partly thrives on the fact that there are highly speculative and/or uneducated investors out there willing to invest in any new offering. Investors must expect IPOs will fail without blame, in my opinion, and diversify accordingly. Unfortunately, the uneducated speculators are the ones that likely lose it all on something "guaranteed" to be hot.
Except that it isn't magic. It is simply a different method of evaluation. Calling this "magic" is the same as calling strict evaluation in C++ magic.
The workflow I've always used:

Open file > Save with new filename > Change new file > Save changes

10.7/10.8 just removes the last step. The only people having issues are those that confuse the middle two steps.

Or, in unix parlance, you cp then vi. Not the other way around.
Looks like it's not just SaaS that is susceptible to major feature disruption.
I'm confused. All it does is make the "bad" behavior the default, but give you the option to revert it if the original file exists somewhere on disk? That's an improvement?

Versioning (and allowing reverts) is awesome, but changing a decades-old idiom to something that suddenly destroys data is...well, scary, to say the least.

Edit: Someone further down the thread suggested that the function be renamed to "Duplicate and Save". That would totally fix the problem - this is a new interaction mechanism, totally different from what we've all been training on for the last thirty years, and it needs a new name. The feature itself is fine, but hijacking an existing operation's name for it is not cool. It violates the principle of least surprise.
Thoughts about distribution, technology, movie-making and business models
But why would you want to? I thought this all went out of fashion after people finally figured out web 2.0 was a hoax.
The word perjury does not appear on that page.
Q&A Over the Merger of Digital Publishing & Social Media
Or choose Duplicate on the old file, don't save the copy/give it a name, and do the work in there.

Since Lion, OS X also internally autosaves files that have yet to be saved. I've had 3-4 "Untitled" TextEdit files that I haven't saved hanging around for months, across reboots.
That is a lucid, intelligent, well thought-out idea.

Overruled.
Bernie Madoff's mistake is that he screwed over other rich people.
I think the title refers to the Knight Capital Group incident which is referred-to in the Editor's note:

One of the most interesting things about the catastrophe
at Knight Capital Group—the trading firm that lost $440
million this week—is the speed of the collapse.
I genuinely don't know. The hacker said it wasn't personal. My guess is that I was a waypoint to get to Gizmodo.
The OP does have details to back it up ... employees had problems getting setup

Ok.. tell me about those employees. How much do they get paid? Minimum wage? What do they do? Do they even require a desk?

A week to setup a desk that the employee doesn't even need because they are required to travel constantly is not a problem.

You're taking this awfully personally

I'm not taking any of this personally. You're just sensitive because someone is suggesting that an IT dept might have required cuts.

Geez.. for people who are so scientifically-minded, you sure do seem eager to take everything in the article on faith.
It is only effective against people the party doesn't like. State sanctioned fraud is less frequently punished.
Do you enjoy watching those matches? Looks like an enjoyable sport to practice, but as an layman watching on TV, it gets very boring, because I can't see when someone touched, when someone defended, etc.

At least if the swords where painted in bright colors...
"but the fact that it takes years for the effect of reduced quality to become obvious: in the short term, consumer confidence in the brand is still high," The only thing I'd point out is that the two are related. Sears had this policy for a very long time and so it slowly becomes an established fact. That's why you can make the cost savings change and show new profits for a quarter, 2 quarters, maybe even a year or two. Most likely the "smart person" who made that decision gets promoted onto another group that needs better margins. Then the wheels come off but the exec is long gone onto something else.
I think his mea culpas for Rage were a far more interesting topic than the Linux stuff.
Twitter must tackle trolls say police
And you could even add 2-factor auth to just this secret email account for added measure.
Grapeseed oil is expensive. It's a better oil than canola, especially for something like mayo.

I believe it goes rancid though (just like canola) after a time so you should continue to buy in small sizes.
Most likely the top comment that tries to impose as a fact that the US and Chinese legal system are equally unfair.

Stating these kind of absolute, unproven, personal statements as absolute facts is (was?) frowned upon around here.
I just wipe it off with a wet paper towel. I never notice any residue or flavor doing that. I figure if I'm not tasting the vinegar I spray on after, I'm definitely not tasting some dish soap.

I also use a very light natural dish soap. YMMV if you're using one with strongs scents/chemicals.
I don't know if this is really done by Stack Exchange. If you look at the user 'Stack Exchange' it has an arstechnica e-mail associated with it.
I don't know if tragedy is the right word for this. We live in an era where the marketplace has more of an effect on the trends in computing than academia. Nothing tragic about that.
Yeah I also don't get what the significance of "edited" is supposed to be, it just reinforces the image of the model not having changed.
No, but you might get enough heat from tidal forces.

(like here: http://en.wikipedia.org/wiki/Io_%28moon%29#Tidal_heating )
There are bad executives like their are bad programmers. You should narrow it down vs being so broad.
Oh this is priceless, "I wanna bubble! I wanna bubble! Waaaaaah!"

TL;DR version : Companies go public later, non-qualified investors don't get a chance to invest during their growth phase, so 'regular' folks are missing out on that wealth creation.

All of that is true, and 'regular folks' are also missing out on the wealth destruction. The author uses FaceBook as their stalking horse, they point out that people who invested when Facebook was only valued at 550M have done really well, and people who bought at the IPO price or since, haven't. But here is the rub. Is Facebook a good investment or not?

If you have any sort of maturity as an investor at all you realize that more money is made by the real growth post IPO than is made leading up to the IPO. That is because it occurs over a longer time and starts from a bigger base. If you had invested in LinkedIn at their IPO (they have a credible business model, and traction) even after the 'pop' you would have paid between $90 and $95 a share. That same stock today is worth $108. That is a 13% gain in a bit over a year. Pretty good in an otherwise stumpy economy. If you bought Stratsys (NASDAQ:SSYS) last year like I did because I thought "gee, I think 3D printing is going to be a huge growth industry." You could be up 200% (I bought it around $25 and its up over $60 now.)

The bottom line is that nothing 'bad' has happened to 'investing' but we appear to have successfully avoided re-creating the dot-com bubble craziness of the last century.

But the author, perhaps reading glamorous stories of people who talked about how many 'Porsche units' of money they earned on their over valued stocks that day, has come to realize its not going to be like that. Ideally not ever, but at least until the old farts die who remember how crazy it was. Going middle-class => multi-millionaire => middle-class does something to a person. Maybe it turns their cynicism dial up to 11, I can't say for sure. But there is no sense complaining about not having a bubble happen.