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.
> 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.
> 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.
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.
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?
> 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.