Readit NewsThere doesn't appear to be that much spare capacity, at least on the 7010's FPGA, around 2k cells IIRC? Certainly won't be creating a bitcoin miner in that :-)
Still the most interesting bit of hardware to come down the pipe yet.
At first glance it seems like a backward move to me, but i'd be at least willing to give the idea a try.
GNOME 3 takes a lot of heat, they're one of the few actually pushing the envelope so it's to be expected i suppose.
A little more encouragement and a little less boring complaints "stating the obvious" would go a long way.
How wrong was i. Consistently one of the best feeds in my feedly these days.
All this does is say "while you figure that out, put it in a script". First, it means we can test the dependencies easily by re-running the script to see that it actually accurately reflects what needs to be done.
Secondly, when you're done, you have a reproducible deployment environment that massively simplifies ops and dev: Ops can decide on upgrades, re-run the scripts, have QA run their tests and know the upgrade won't break stuff in production. Dev can make code changes and be confident that what they hand off will actually work in the production environment because they've test deployed it on VMs built from identical templates.
As long as your team can figure out how to deploy the software they write, they can do this. If they can't, you have bigger problems.
Here's a rather contrived example but it illustrates the idea i'm getting at: "Will the inventory agent software be able to login to audit this container environment when they're done building their release?"
As far as I am aware, folk aren't really writing distributable applications that target the VM up. You can get preconfigured stacks, or you can get standalone apps that you install in your environment.
But nobody's said: "Hey, if we control the app design from the OS up, we can make it much more intelligent, robust and at the same time sweep away a lot of unnecessary inner platform nonsense".
In terms of the slides, my approach is to reduce the NxN matrix by eliminating a lot of the choices. Why write your blog engine to support 5 different web servers when you can select and bundle the web server? Repeat for other components.
It gets better. Why write a thin, poorly-featured database abstraction layer when you can take serious advantages of a particular database's features?
You can't do this if you write under old shared-hosting assumptions. You can do this if you target the VM or container as the unit of design and deployment.
Yes, this is one of my bonnet-bees, since at least 2008: http://clubtroppo.com.au/2008/07/10/shared-hosting-is-doomed...
Most developers are not full-stack aware - nor should they be. Having a pack of generalists drive a product is sure to reduce momentum.
Better that the contract is "here's a platform you can deploy to" than "here's some CPU time, break it and you get to keep both pieces"
I've never found a better tool for communicating what to do and in what order. Everyone just understands them, with zero training. You can even play with the format slightly and people still get it, e.g. break out a formal time column? Sure! People just start using it.
I especially like them for high pressure situations. E.g. for handling prod outages i've consistently found checklists work better in practice than flow charts, knowledge bases, call trees... etc.
I use them for many things, from the fairly benign (releases?) to the relatively rare (new joiners).
I recommend, just based on my experiences so may not apply in all environments, using a simple web based app to handle all your check lists. It'll be accessible from any device, without installing anything up front.
A couple of small extra features will make it infinitely more useful:
1) Allow for both a "ticked" / done status and a "working on" / "i've grabbed this one" status. Display the user who's grabbed it and the time they grabbed it.
2) Allow for checklists to have all their boxes reset on a schedule, e.g. daily reset of the "start of day" check list.
3) Archive completed checklists - they capture useful information about who and when, so I don't bin them when they're completed
That said, the ISPs objections are likely cost, rather than protecting freedom. Much like Camoron, this is pandering and nanny stare, rather than really caring about children. To him this is a tick box ticked which costs the treasury nothing, he gets the ISPs to pay for his votes.
All quite seedy.
And rightly so. If this goes through, i'd like to see the ISPs add a line item to everyone's bill calling this out in plain sight to all their customers. "This month you paid an extra #1.75 to cover the costs of Government censorship infrastructure we're required to purchase / install / maintain.
I wonder if it could be set to lock at boot unless your phone (or BT headphones or whatever) is nearby.
I doubt this can be all that secure since it can be downloaded from the App Store, I'm pretty sure that means it can be force quit (it could not prevent this key combo since its restricted in the sandbox). It may be just enough.
But here is the thing that irks me about this. On the server end of things Netflix has been a rather amazing contributor to open source softwares. This boycott seems rather like shooting your self your own foot to stop an intruder.
Netflix are part of the content industry, it's not that they're the best of a bad bunch, they're actively more open than some artists.
Subject: [Freind]'s invitation is awaiting your response
Body: [Friend] would like to connect on LinkedIn. How would you like to respond?
[Photo of friend] Confirm you know [Friend]
... and ...
Subject: Invitation to connect on LinkedIn
Body: [Photo of friend]
[Me],
I'd like to include you in my network to share updates and stay in touch.
- [Friend]
All emails sent from friend's email account, not LinkedIn. I've confirmed with friend that they were completely unaware of this and were quite embarrassed.
Not cool, LinkedIn, and most definitely dishonest.
An example: I had a real life connection to a trainer, i studied for an industry qualification with him. I had zero online line connections to him. Somehow linked in put us together.
His profile mentioned nothing about taking that course, mine mentioned nothing about attending his course. My work handled all the procurement side of things so he had no access to my email address or anything like that.
In credit to linked in, this guy happened to be the best trainer i'd ever studied with so i was actually pleased to see the recommendation. Still wondered how they managed it though!