Often with Tesla, year people leave at lunch to go to the nearest supercharger. If tracks added some fast DC chargers, it would be a nice boost.
641 karma · joined July 26, 2009
Often with Tesla, year people leave at lunch to go to the nearest supercharger. If tracks added some fast DC chargers, it would be a nice boost.
It was something that had always passed and never been an issue on 1.0.3, but started failing 85-90% of the time on Go 1.1 with no code changes. :(
On our main codebase, we experienced some major issues when moving from Go 1.0 to 1.1 from this exact issue. We had a goroutine that was doing some remote calls wrapped with a timeout, and the call was consistently timing out even though the remote service was perfectly fine (it was another service on the same box).
We found the cause was another goroutine running something in an for loop that didn't do anything that would allow a pause in execution for another goroutine. So, the scheduler just obsessed on that goroutine, running none of the others until that one was done, and by then the timeout on the remote call had expired.
We fixed up that case, but also found a few others were we simply added a very small sleep call... for no other reason than allowing the scheduler to evaluate other goroutines. Meh. It made sense when we finally tracked it down, but was one of those things where we had to pause and ask "really?"... and adding a sleep call with comments "yes, I am really calling sleep".
Soon™
We didn't write our own HTTP server, but rather a framework that sits on top of it and makes it easier to use.
The logging library is quite unlike anything else we're aware of, and the goals of it were language independent. The author of it is giving a talk about the library and our experiences with Go at GlueCon next month.
The ORM is the one which is more a result of what we wanted not being represented by existing libraries, and the community being still smaller compared to Node.
However, with all those still considered, we've gained a lot of velocity with Go, better concurrency without doing full async development, etc. Personally, I've hated testing async code in the past with both Node and EM+Ruby.
The "15 minutes" part was hyperbole.
The timeframe referenced the length of the discussion of the two, not the knowledge the decision was based on. Several of us had previous experience with Node, and some of the team had prior Go experience.
I see irony in the "getting hacked" part. But seriously, if he is more experienced, then why do they have machines unpatched like that for 6 months?
"it seems it was indeed a kid who did not understand how to install a proper rootkit and cover up his tracks"
It is rather bold to be posting about how you just got hacked by not applying simple patches, and to then bash the "kid" who couldn't install a proper rootkit.
However, when I get home and get back on my system, then I'm ready for night time mode.
I prefer the 20 second switch over so I know to turn it off fast. With the long transition, I find myself being annoyed for a while until its enough for realize I need to turn it off.
I'd love a simple "activate at sunset, but not before X:XX".
Going under isn't the only concern. A free service which most certainly costs them (bandwidth, power, rackspace, IPs). Even if they're small devices, they add up. And an offering that is losing money will get bumped for an offering that is earning money.
I'm mainly just predicting the future HN post. Panda tears will flow. Just think back to Joyent cutting out the old TextDrive lifetime hosting. People more than likely got their money's worth out of it, but still a large amount of drama.
Sure, you pay to get it back, but they even mention "probably does not cover our costs" for some.
You send them your own Raspberry PI, at your expense, for many probably over seas/out of country. You pay them nothing for their service. They're Yet Another Hosting Company.
Wait until you overuse some resources, they're late paying their data center bill (not sure how IP allocation work over there, but RIPE has their IP space, not them), you Pi for some reason goes offline, or the company goes under.
There is no free lunch. Just wait, it'll be proven again.
OpenVZ is more OS virtualization, there is less isolation between instances.
OpenVZ usually has "guaranteed CPU/RAM" and "burst CPU/RAM", while KVM always gives you what its assigned. The guaranteed/burst is typically BS. More often these budget providers like OpenVZ because you get greater density, which means more noisy neighbor and taxed resources like disk IO.
Rackspace, HP Cloud, VPS.NET, Gandi, RIMU, Slicehost (back in the day), Webbynode, Liquidweb, StormOnDemand (though a part of Liquidweb), Burst.net, PowerVPS, FDC Servers, ...
List could go on. I usually look for whether they have an established history, a site that doesn't look like a crappy overused template, a real physical address, WHOIS info on the domain, Google them and research, whether they have a real status site, maybe lookup if they have an ARIN number, traceroute to their site, etc.
This comes from my own experience running my own small scale VPS host for a few years, with a purposely small customer base (mostly people I knew personally).
Look at WHT and follow it for a while. That market is crowded, a race to the bottom in pricing AND support, and is full of drama. Some examples I've seen:
* Lack of experience in production systems with no backup procedure... some systems go down, they loose all data, entire business caves.
* Super tight margins and low capital... fall behind on a build, their provider shuts them down (most these guys are leasing dedicated servers or reselling from another provider)
* Don't know who really is in control... reselling from someone and don't know who? On dedicated servers with a provider who is known for a problematic network?
* They're some 16 year old and their dad grounds them from the computer so they can't answer support tickets.
* Don't understand the technology they're using for virtualization and get noisy neighbors, don't properly secure exploits, don't understand the inner working of their COTS control panel, etc.
* Look up the history of Lxadmin. VERY popular control panel package, company behind it, but most coding/knowledge behind the CEO. Big exploit found, 100k servers exploited, CEO commits suicide. Company is dangling. Believe licensing servers went offline. All providers using them were screwed. They were using COTS software, didn't know their own stack, left scrambling.
Stick with providers that are a real company. Employees of their own, support staff of their own, own their own equipment, etc.
Linode is great, EC2 is great, and there are several other providers.
I am not saying those are bad, but with more established DBs like MySQL and PostgreSQL, you never really saw the same kind of marketing efforts towards developers, startups, etc. It is kind of a newer concept.
Didn't expect to see this on HN. Interesting the differences in comments between here and /r/eve.
I use Recurly for one of my SaaS apps. I've had it on my todo list to move off of them and just use Stripe directly, but changing entire payment backends isn't one of those "lets hack for a few hours" things. Just using Stripe would be cheaper than Recurly and my existing merchant account/gateway.
I don't know if any of my customers are affected yet, however now they have failed to bill a customer when they should have, double billed a customer when they shouldn't have, and now potentially lost data.
I'm still on their original pricing plan and never moved to the new plan. When they changed their pricing, it just didn't seem attractive. My service is too small and my month charge was going to double for a service I was already meh on and just adding some new reports.
I believe at one point I'd heard you can request customer data from them... don't know exactly how that works as exporting customer credit card information would be incredibly sensitive. If they've lost any credit card info, likely just cut my loses with them, export nothing, and have all my customers resub. Probably not going to like that, but so be it.
Now 5 comes out, seemingly has better retina support, and I'd have to shell out $50 again. No thanks.
Each Fusion release is less and less compelling for the most part. Fusion 4 was "built for Lion", yet I used Fusion 3 on Lion exclusively until June just fine.
I think the OP's idea is great and can go further. The distinction is between what I am doing/need to do and who I am.