Ha me too, you are not alone. Then again I used the word exotic for esoteric for many years, I wondered why people would always deny the solution was exotic in a giggly way as i loud ranted everything was too damn exotic. etiquette was another source of laughter, at 33 i finally figured out how to say it correctly. shit happens!
chrome did not have extensions when launched, and firebug was far superior back then. it was a long time before extensions came maybe even 2010. they did not run with what ff did, far from it.
I bet you've been pretty privileged in grand scheme of things, university, regular jobs, maybe the lowest point has been backpacking etc... Parent have at least one car, yawn yawn yawn.. No one is stealing from you, they are stealing from a supermarket. Privileged people always seem to think in black and white, theft is theft never an excuse blah blah, quite often making the cliche mistake of associating morality with legality.. I hope one day you don't need to learn this ain't always correlated..
I thought that may of been the case, that could explain why the same phone is 50% higher in price now than 12 months ago, at least in BKK. I wont lose sleep over Intel selling chips below cost.. On the mention of diary.. milk these offers when they come along..
Me too, had this device for 12 months now, and it just flys, always put it down to the intel cpu given how I only paid ~160usd for the device. New samsung devices at higher price points, j5, j7 are slow dogs in comparison. so does this mean a dead end for x86 android? Ill stick with Asus thougj given the frequency of firmware updates, and all round solid hardware.
Probably the worst code I've ever seen, copy and paste gone crazy, buggy as hell in tracking where it is up to, just nasty and I really wanted to like it. Refund was no problem though.
Too early to say, but unlikely in my opinion. I expect VS code to continue to gain features and language support, one day we might even see a R# plugins for it but I don't expect it to bring Windows heavy features like WPF/xaml and Winforms across. Apparently C# and F# story on VS code is already pretty solid for server side apps
How much does cash handling costs, counting/paying in, insurance, fake notes, transport to bank, uninsured risks, shotgun robberies, still be less than 3% but not far off imho, we need something smarter than cash but not from giant ripoffs such as mc/visa/amex
Thanks to our friends at cPanel and the hundreds of thousands of web hosts that embrace and evangelize the platform old-school insecure FTP is still popular and strong and often the documented/default way clients are encourage to upload their files.
A candidate with active LinkedIn profile can be seen unfavourable in many industries as peeps spill too many details of projects in order to glorify their profile, one can learn a lot about competitors ways of working and technology just by reading employee profiles. Not on LinkedIn, one headache saved...
I always love reading about event sourcing, the different approaches and trade offs, hoping one day I can use it, somewhere...
But I never thought somewhere would be PHP where it is essentially build the world and destroy the world per request. I would of presumed PHP would be poorly suited for event sourcing since you have no in-memory cache to help optimize performance. Thus for any accepted command where you have to revive the aggregate then you need to load and deserailize a snapshot (if one exists), and then deserialize any subsequent events and replay them, before you can apply the latest event to the aggregate. Does this concern you?
However removing a layer of caching probably simplifies a lot of things, and being completely stateless I guess could make scaling the app layer easier. One thing that's not clear is how you handle locking of the aggregate (unless you restrict php_fpm to one worker process)? Also the order in which you handle event persistence, shouldn't the event be persisted first before dispatching on some bus, what happens if the server crashes prior the persistence but after a dispatch where something interesting happens?
Animations look tidy and I'm sure you learnt a bulk of CSS3 in the process and hopefully had fun, but Im not going to include 558 lines (517 sloc) 26.9 KB to get animations for hamburgers that change to X. Infact it's not even the size it's the added dependency and risk of such dependency (as browsers evolve) that concerns me.
I also didn't find the last one jarring, why would it take more than a blink to slide out side menu (or vice versa) on an SPA unless doing some ajax loading for side menu content (can't see why this can't be avoided though)?
Serious businesses with algos that need snapshot "now" views of this information will probably get this information from a financial data provider I imagine, Bloomberg? Reuters? or give relative infrequency of change (max few times a day?) perhaps internally by feeds managed by their own researcher/analysts.
I can could see some use for non-trading researchers and analysts, or even on the trading side for very small shops, by being able to grab historical information, perhaps applying some aggregation over the data too, but surely it's already available. Where do you get the data from?
This article has been about for a while if I recall correctly, remember adoption is always optional, and in many cases your direct exposure to Docker [images] and it's perceived limitation is pretty limited. I am really liking Kubernetes at the moment and high-level concepts it embraces around container management, my exposure to Docker is limited to the image format (and Docker hub until I sort out a private registry), it's a minor implementation detail to me at this stage and none of what this article writes concerns me too much.
Evaluate docker and containers and any orchestration software in general on how it fits with your systems/values/requirements, the author talks about not being able to run his archaic insecure FTP server due to not having 15000 random ports available, right there I knew we are different people with different requirements..
In 2016 we should really be boycotting FTP if we choose to boycott free/open software...
I don't think it's ever best practice to inline significant amounts of javascript (aside from bootstrapping code). Inlining CSS might be viable based on some recent HN articles, but a SPA generally has a non-trivial amount of javascript code and dependencies thus I can only forsee disadvantages even if you make the inlining part of your gulp/grunt workflow. You can add long-live cache directives to your javascript sources and bust them with a checksum/date/revision e.g. ?v=abc123def
I suspect battery drain would be a bigger concern during the SPA running time, is it polling, does it use requestAnimationFrame for rendering, is it doing a non trivial amount of work client-side etc..
Unmentioned in the article - Curl supports --resolve, this single feature helps us test all sorts of scenarios for HTTPS and hostname based multiplexing where DNS isn't updated or consistent yet, e.g. transferring site, bringing up cold standbys, couldn't live without it (well I could if I wanted to edit /etc/hosts continuously)
Have you considered a VPN to a Singapore provider. e.g. PureVPN or alternatively PPTP on a DigitalOcean, Linode (maybe not in this case), Softlayer etc.. Generally VPS provider will have better international transit than your local ISP, however your local ISP will peer in Singapore so that part is usually congestion free.
Is there a global status of cut/degraded undersea cable systems? That would be very beneficial. It seems that the connectivity providers Level3, Hibernia/Atrato, HE, NTT etc.. only relay limited information, perhaps their notification from cable providers is very limited too, by the time it gets to downstream customers we're all guessing, e.g. on WebHostingTalk there are customers trying to determine latency issue to a Hong Kong provider, only to have a competitor announce a fiber cut 2 days ago in Jakarta may be affecting it.
The article talks about the design choices as the reason for success but I think the expense of the chair and need to perceive some related value caused the, in my opinion, over-rated reputation, coders attributing their 14hr marathons and their 10x factors to some chair, in some instances their new physical posture, tone and health all due to the magic of a $1000+ chair.
In my experience having worked in an office which was all Aeron chairs for several months I feel no different now on this $100 office mate chair or any of similar priced chair at the various co-working places I visit. I should note too Im not exactly in great shape.
tl;dr - price and talk made the Aeron chair an icon
This is interesting, one thing that does concern me though is the fingerprint of the traffic, is this "impossible to shut down" presuming ISPs don't analyze their own users traffic and don't apply restrictions to such in certain circumstances. For example ip traffic unless to a dst of 80/443 with proto tcp (or 53/udp dns) could be classified as potential-P2P and throttled. Or if residential ISPs don't let end users run servers possibly by something as primitive as a router ACL on ports <1024, and then throttle P2P where src port and dst port both > 1024 then how will this survive?
It sounds like this solves the discover-ability issue, but weather it can be crippled vs shutdown Im not so sure.
Also does this have anything to do with popcorn time, looks very similar, movie time :)
dotCloud provided infrastructure (compute nodes with memory/cpu limits), which they wanted to quickly distance from. Docker Cloud is BYOI (bring your own infrastructure) such as Digital Ocean, AWS, Azure, Softlayer. It's basically Tutum out of beta, similar to CoreOS tectonic but less enterprise targetted (pricing upfront, freemium, can use $5/mo DO droplets). It's a managed control panel essentially. CPAS - Control panel as a service?
I liked Tutum (and thus Docker Cloud) as a rapid path to get up and running, but the higher level concepts of Kubernetes appeal more to me for real worl projects.. (note: Kubernetes uses docker and docker images)
It is important to note that it has only been ~8 months since Kubernetes v1 release and with <100 respondents one can't take too much away from the Feb survey. Comments in column I are interesting though, a lot of people still seem to be "figuring it out"... Kubernetes 1.2 and onwards ftw :)
I've found complexity and/or/aka too many features discourage adoption, this was particular painful when a previous company I pushed to purchase Axosoft quickly abandoned it - nobody (including me eventually) could be bother using it. Hence easy to use, easy to get going, 'where 90% is intuitive' tools like Trello and Basecamp, arguably deficient in many formal project management areas, continue to attract and maintain customers. Combined with skype, hipchat or private slack for realtime communication seems to solve most of the headaches. A client recently added freshdesk to the mix too, again for 90% its intuitive.