For me, the compelling part was at my last company, we'd build these complicated distributed systems with a whole lot moving pieces—any of which could go down at a moment's notice. For a complex enough system, there was sometimes more work to be done to deal with any part of the system failing than to build the system itself. Basically, we were implementing our own bespoke version of Temporal over and over again.
To your point, the complexity of a SQL/PHP application is significantly smaller, but, the value proposition of Temporal is probably still there: If any part of the checkout process fails (e.g. charging the credit card, successfully triggering the order after they've charged the credit card, timing an email if there is an abandoned cart, handling the moving pieces of a return). These pieces are either handled manually by a human or you've got a decent amount of business logic in place to handle each of these edge cases individually.
The value-add of Temporal—in this case—would be that it would keep track of where the customer/order was in the overall flow of ordering something and pick up where it left off in the event that something went wrong.
I haven't had a chance to download it yet, but my suspicion says it's probably an Electron application. What do you all feel about this practice of taking long-lived web applications and getting them out of a tab and into a desktop shell with a place on the dock/task bar and the ability to Atl/Control-Tab?
Here is my take on what SendGrid does: Sending an email is pretty easy. Sending a metric butt ton is hard and so is hooking it into your app. So, we help you with that because screwing that up could be very bad.
If you have any problems, open an issue on GitHub (jennschiffer/make8bitart) or tweet at @jennschiffer. She's about to have time to work on stuff soon hopefully.
This article is pretty amazing in how poorly researched it is. I'm submitting this less as a piece of news and more as a piece of evidence of how dramatized a well-reasoned decision in open source can become.
That's good to know, thanks. -X doesn't work at all using the Raspberry Pi. If you have any insight, I'd love to figure out how to get it working with -X, but all my attempts are unsuccessful. Granted, I haven't spent too much time with X11 and its brethren since college.
No, I believe it's saying that any split that was not caused by a swollen battery is out-of-warranty. If it was caused by a swollen battery it would be eligible for an in-warranty repair.
I don't think it came as a surprise to terrorist organizations that the NSA was working to break their encryption techniques—just as I'm sure it wouldn't have been a surprise to the Soviets during the Cold War.
The group that was surprised and caught off-guard was the American people.
It's been just over a year since the Snowden leaks. Overhauling an entire communication system likely took more than a year. Ground-up rewrites rarely go that well.
This strikes me more as a publicity grab for this firm than any kind of objective science.
I'm getting too old to care what platform (language, framework) other people prefer, but I suspect that if you were to go to any given web development conference, empirical evidence would not square with OS X being "unsuitable" for web development. Beyond that, I suspect you could web development done on pretty much any desktop OS these days. I'm sure you could do web development on Chrome OS, if you wanted to.
This strikes me more as "This is different than what I'm used to!" or "I don't much care for this." than "This is unsuitable." Emacs is available on OS X. Beyond the initial server configuration, I'd say the large majority of packages your average web developer is installing are from NPM, RubyGems, CPAN, etc.
I asked Github and Sass and CoffeeScript support will apparently also work for regular (non-Jekyll) pages on the `gh-pages` branch if you put dashes at the top of the file you want to be processed.
Amongst my many issues with recruiter spam, one of my biggest pet peeves is when recruiters send me emails about jobs without telling me who the company is or what they do. That's kind of a big deal as to whether or not I'm even remotely interested in the position (I'm probably not).
To your point, the complexity of a SQL/PHP application is significantly smaller, but, the value proposition of Temporal is probably still there: If any part of the checkout process fails (e.g. charging the credit card, successfully triggering the order after they've charged the credit card, timing an email if there is an abandoned cart, handling the moving pieces of a return). These pieces are either handled manually by a human or you've got a decent amount of business logic in place to handle each of these edge cases individually.
The value-add of Temporal—in this case—would be that it would keep track of where the customer/order was in the overall flow of ordering something and pick up where it left off in the event that something went wrong.