drgath

That sounds amazing. Off-by-one disasters, time conversion problems, imperial instead of metric messups. Halt and Catch Fire & Mr Robot were great. We need more like that, and less like CSI:Cyber.

Seems likely it’s all there.

https://www.fdic.gov/news/press-releases/2023/pr23016.html

> As of December 31, 2022, Silicon Valley Bank had approximately $209.0 billion in total assets and about $175.4 billion in total deposits. At the time of closing, the amount of deposits in excess of the insurance limits was undetermined. The amount of uninsured deposits will be determined once the FDIC obtains additional information from the bank and customers.

Have we yet deviated from FDIC rules? I don’t think so, even with what Yellen says. My limited understanding of the situation is that the assets to cover everything is there, they’re just tied up in long-term treasuries.

From the FDIC’s site:

> As of December 31, 2022, Silicon Valley Bank had approximately $209.0 billion in total assets and about $175.4 billion in total deposits.

For simplicities sake, let’s just assume 100% of the assets are actually there, but it’ll just take varying years for everything to mature. So, what’s next? FDIC finds a buyer for the assets, perhaps a private bank or a a pseudo-government body who has the ability to wait till maturity, and in the meantime, everyone gets all their deposits. That’s not a “bailout”, and is following the rules.

ctrl+f “yql” and landed here. Was an amazing service for its time. Could even execute server-side JS in its engine (Rhino). Certainly the only E4X environment I ever coded in.

Asking someone to spend $400+ just to upgrade equipment in order to support a service that doesn’t work well on the original equipment you sold them, takes some guts.

In 15 years as a professional software engineer, I’ve never worked somewhere that wasn’t heavily using IRC, Hipchat, or Slack. The conversations are identical, the only thing that has changed is the service being used. As previous poster alluded to, your complaints aren’t a Slack issue, it’s a co-worker issue.

To the same degree? I disagree there. I would never expect a full-stack engineer to be more proficient at front-end when compared to a FE specialist. You are expected to know some, but not to the same degree. That’s the reason they are specialists, in comparison.

Reminds me of YQL, https://developer.yahoo.com/yql/.

They’re about to IPO. Doesn’t mean they’re profitable, but it does mean their finances are healthy enough that they can be publicly traded.

> Being overworked is an excellent reason to hire. It shows that you are about to lose your team due to burn-out or extended sick leave.

I took the original comment to imply that when employees are overworked, it is due to a failure in planning to assure a project is adaquately staffed from the beginning. That is when you should hire, not because you just began to notice you failed to plan appropriately.

Sure, if someone is being overworked, hire to spread the load (if new person can ramp-up fast enough). But don’t put your employees in that position to begin with, because some of them won’t return to full productivity, even after you resolve the problem. Overwork for any duration comes at a cost.

Sling[1] is the closest we can get right now. Eventually, channel subscriptions will be available through something like an App Store and just as easy to manage as an recurring subscription app.

[1] https://www.sling.com/

The current state of the lawsuit isn't over the novelty of function, it's about the copyright of it. Also, very important to their argument is that this wasn't some random developer at Google who added it into Android, it was the guy who had added that function to OpenJDK.

While I also disagree with the lawsuit, if you are coming at it from the mindset that code you have a copyright to was used elsewhere, Oracle has a compelling case. Certainly not a $9 billion case, and not one that takes up 6 years of time to decide, but that's not for me to decide.

Can anyone explain what prompted Six Flags to buy 100 of these, or what has everyone excited? First-aid vending machines aren't new, nor are these products that Six Flags doesn't currently sell. You can already buy some of this stuff at gift shops, and everything else is (and should be) handled by EMT on site.

Not saying this isn't a novel idea, just haven't wrapped my head around the business model that hasn't already been done before, so I feel like I'm missing something. Is it increased visibility in park leading to more sales? Ability to eliminate some EMT staff? Ability to charge people for supplies instead of giving them away?

Many scientific studies confirm common sense. It's the process of turning assumptions into fact.

> but I feel like the Open Source community could do itself a lot of favors by avoiding this kind of tone.

To be accurate, that comment was from a security researcher at Google commenting on a closed-source software project. I agree that the tone of the comment was not beneficial, but I don't view it as being associated with or reflective of the open source community.

Forget the specificity of Micky Mouse, as that character just represents Disney's brand. Do you really think a company should lose their brand after X years? Disney doesn't care about Steamboat Willy, they care about people selling knock-off mouse ears, which comes with Willy entering the public domain.

I was just listening to an NPR segment on how Elvis Presley's image has become tainted by cheap crap, and that inspired Frank Sinatra to ensure the same doesn't happen to him. His biggest fear was that his face would be sold on a coffee mug. Should anyone be able to do anything with Frank Sinatra's likeness now that he's passed?

Should the estate of George Lucas be able to create new Star Wars movies in X years to compete with Disney's Star Wars movies in effort to undo everything they added to the universe "Because it wasn't George's vision", even though he sold off the rights?

I know I'm throwing hypotheticals and edge cases out there, but I just want us to focus on the issue deeper than "What reason is there to keep Steamboat Willy out of the public domain?" There's no good reason. But there are tons of good reasons to ensure people can't profit off an active brand's image.

Just to list a few of the valuable properties off-hand: Homepage, Mail, Search, Tumblr, Flickr, Finance, News, Sports, Fantasy sports (including daily fantasy). Some of the bigger ones are billion+ dollar properties. Others are hundreds of millions.

> It's not clear to me that it actually does anything worth paying for at this point.

Few users of Google and Facebook actually "pay" for those services, they're primarily all advertising funded companies.

Entirely dependent on who decides to buy Y! Mail. Safe to assume it'll be around for a while though, since straight killing Y! Mail doesn't make much business sense.

This can be answered by the question "Is Flickr profitable by itself?" If so, someone will certainly buy it. If not, who knows.

My guess, someone will buy it and it'll languish for a year or two as the product strategy is developed and migration of technology occurs, then the new vision by new owners will be executed.

Despite the "wall" between the two organizations from a knowledge-standpoint, there isn't one from a financial standpoint. If you had ambitions to be a $100+ billion company (see: Uber), and think Google might eventually want to compete with you, why would you want to fuel your competitor via your own success?

In 1835, the New York Sun (a serious newspaper [0], 1833-1855) published some articles [1] describing alien civilizations on the moon that can be seen through a new telescope in South Africa.

From Wired,

> The Sun, ever the champion of the public good, claimed, no joke, that it was actually all a public service… to get the nation to stop worrying so much for a second about that whole slavery thing.

So, there are good journalists, bad journalists, "journalists" who aren't even journalists, and they've all existed since the birth of the printing press.

[0] http://en.wikipedia.org/wiki/The_Sun_%28New_York%29

[1] http://www.wired.com/2014/12/fantastically-wrong-thomas-dick...

That's pretty much the approach of Virgin Galactic. Reasons why it works for them, but not for NASA would have to be explained by someone more qualified. I do know that VG barely gets into LEO, whereas NASA's requirements are much higher. In any case, I presume the scientists at NASA (and SpaceX & co) have considered just about every alternative, and the current approach still remains the most efficient for their needs.

Seems far more likely that in 40k years, humans will have discovered the ability of interstellar travel. Heck, at that point we could go out and fetch Voyager 1 ourselves before it comes within 1.6 light years of AC+79 3888. If we can't in 40k years, it's likely not possible that we'll ever leave this solar system. It could be that's it's just not physically possible. But more likely, do we survive long enough to develop that technology?

I've always viewed the Golden Record as a way to make humanity feel better about its future. The need to leave a legacy behind is core to who we are, and that's exactly what we did with those two discs. We left something behind that will survive for 1 billion years, with the infinitesimally small hopes that someone will find it. But, it makes us feel good.

YUI did host its own blog, but it was shut down a few days ago. http://www.yuiblog.com/blog/2014/08/25/weve-moved-to-tumblr/

Along those same line, here's another good read about the recent npm, Inc. investment. Feel free to skip down to 'Open Source and $$$' section. http://words.steveklabnik.com/is-npm-worth-26mm

In short, it's debatable whether an investment into npm, Inc. will directly pay off for the investors. What the investment is more likely about is creating the infrastructure for new, billion dollar companies to pop up, giving those investors an inside track to the new companies.

In the case of ElasticSearch, investing in this infrastructure project absolutely makes sense. "Big Data" is becoming huge, but it's still relatively dumb. Up until now, we've primarily been focused on tools and technologies to source, aggregate, and analyze the data. But lots of companies are now popping up who are built on the idea of making intelligent use of all this data, far beyond what humans are naturally capable of. ElasticSearch of course isn't the whole solution, but it's part of it.

(I work for one of those companies, and we use ElasticSearch)

Considering Atwood's Law, I guess it was only a matter of time until we arrived at this point.

Reminds me of when I worked at Yahoo, and in 2009 I had to track down someone who worked on Upcoming. I found someone who had Upcoming listed in their Backyard profile, but "Oh, I don't work on that anymore. Last I heard {other person} was working on it." So I tracked down that person, only to hear the same response. Following the chain, four or five people and half a day later I finally found the one person in the entire company who worked on Upcoming.org, but only part-time in a community support role. Having recently started at Yahoo, I quickly began to realize what was wrong.

Luckily things have changed considerably since then, and very happy to see Upcoming being handed back to its creator. Same thing should have happened with Delicious, but when they were looking for a buyer, Yahoo (allegedly) refused to sell it back to Joshua Schachter.

As someone who pays Meetup.com $144 a year for my group, I'd love to have a cheaper alternative.

All of that extra cost was R&D, which is currently being funded by Google's advertising. While I have no idea what Google's business model will eventually be with self-driving cars, at the end of the day it's just software and some cameras that can be mass-installed on most any car.

While the cost will initially be higher, it likely won't be much, and will eventually be negligible.

> But how can putting this functionality into an extension package be considered a reasonable design choice?

I like the design of Atom, because it allows me to freely compose an editor that does exactly what I want, and nothing more. While multiple panes is a requirement for bpicolo (and you?), I use multiple panes in Atom (my primary editor) and haven't felt the need to resize them. Am I the minority, or are the others? Or is it 50/50? Basically, we don't know until the editor has time to grow, and its community has a chance to dictate what features are required.