|
I sometime wonder about the quality of my code. Think I make the right decisions, but is there a better way?
|
|
|
|
|
Go was designed and developed to make working in this environment more productive. Besides its better-known aspects such as built-in concurrency and garbage collection, Go's design considerations include rigorous dependency management, the adaptability of software architecture as systems grow, and robustness across the boundaries between components. This article explains how these issues were addressed while building an efficient, compiled programming language that feels lightweight and pleasant. Examples and explanations will be taken from the real-world problems faced at Google. Software designed for problems beyond "web scale": Google scale.
|
|
|
|
|
I’m going to use Internet Explorer 10 as my primary browser for one week. That’s one week without browsing, tweeting, or listening to turntable in Chrome (current “Browser of Choice”). That’s one week deep inside the bowels of the browser that burned me, and so many of my peers, so badly over the last decade. One week in the heart of the beast. Why? Isn’t Internet Explorer supposed to be a thing of the past? A bad phase in the history of the web that we’re slowly recovering from? Microsoft has come a long way with IE, and it deserves a second look.
|
|
|
|
|
There’s a common mathematical ratio found in nature that can be used to create pleasing, natural looking compositions in your design work. We call it the Golden Ratio, although it’s also known as the Golden Mean, The Golden Section, or the Greek letter Phi. Based on the Fibonacci Sequence... the Golden Ratio describes the relationship between two proportions. Fibonacci numbers, like many elements found in nature, follow a 1:1.61 ratio - this is what we refer to as the Golden Ratio, and as it forms such a common sight in nature, it feels pleasing to the eye when we use this same ratio in our design work. From Da Vinci to da web, it's a nice way to da-sign.
|
|
|
|
|
Microsoft's Windows Blue update to Windows 8 makes it increasingly clear that Microsoft wants to kill the Desktop. That may seem self-defeating, but there's method in Microsoft's madness. Here are three reasons I think it wants to eventually kill the Desktop. It's all about WinRT now? Who does that help?
|
|
|
|
|
Terrence Dorsey wrote: Who does that help?
Microsoft. The cost of deploying a don't-call-it-Metro app to a Windows 8 device is noticeably higher than the cost of deploying a desktop application.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
You might've read some headlines today—in very reputable publications—saying that there's an online attack underway. The biggest in history. Enough to slow down the internet. This would be exciting and scary, except it's just not true. This would be so terrifying if it weren't advertising.
|
|
|
|
|
The SAGE system was designed to solve a data fusion problem. Radar installations across North America kept watch against Soviet bombers. These needed to be networked together and coordinated with air defense missiles and interceptors. Seems simple, right? In the 1950s and 1960s, this was not simple.... No group of people could really make the decisions in time to mount an effective defense. You needed some kind of computer to make the decisions. These giant electric brains took up an acre or so of real estate, and were encased in huge windowless concrete pillboxes all over the country. Plus, 3 engineering lessons from the SAGE project.
|
|
|
|
|
|
Since Microsoft has publicly acknowledged the existence of "Windows 'Blue'", there has already the first video made its way out to the web.
The german computer magazine chip.de has posted[^] it on their website.
Edited title so it doesn't look like a repost from Ravi
|
|
|
|
|
I glanced through the video and didn't see them show an option to remove "what-shall-not-be-called-metro" (a la "turn windows features on or off->[Insert MS Crap here: IE, Media Player, Media Center etc]").
there's nothing new in "Blue" then, eh?
|
|
|
|
|
bitterskittles wrote: there's nothing new in "Blue" then, eh?
You can adjust the size of the tiles forming the metro %whateveryouwanttocallit%. Plus, I assume many of the imptovements will happen "under the hood", as they did when they realised they made a mistake releasing Vista.
Don't get me wrong, I like Win 8 and Metro. And I don't miss the Start-Button, I hit the windows key, type the program name and hit Enter. The program launches. Nice and easy.
|
|
|
|
|
I especially like the new feature at 2:15 (3-part split screen), makes Metro apps looks less wasteful with screen space.
Also most features in the video kinda have the "this should've been there from the start" feeling. Granted MS users are already familiar with this I assume
|
|
|
|
|
szukuro wrote: "this should've been there from the start" feeling.
Most of us know this feeling from the Vista / 7 story... Sadly .
|
|
|
|
|
Much of which was that by the time w7 was out the 3rd parties had finally updated their code past XP. Drivers (video, audio, printer) were rewritten and optimized for the 6.x kernel; consumer apps no longer blithely assumed they would be running with admin rights when they didn't really need them; etc.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
The following post is a comprehensive summary of the developer-facing changes coming in Java 8. This next iteration of the JDK is currently scheduled for general availability in September 2013. At the time of this writing, Java 8 development is still very much in progress. Language features and APIs may still change. I'll do my best to keep this document up to date. A comprehensive list of exploits will be available sometime after you deploy...
|
|
|
|
|
I wish them the best of luck but I have had no ramifications from turning Java off on my computers and it will take some convincing before I turn it back on!
<sig notetoself="think of a better signature">
<first>Jim
<last>Meadors
|
|
|
|
|
@Jim- Java in your browser (that is, running an Applet) is beside the point.
|
|
|
|
|
Short of a gun against my head nothing will convince me to move to either Win 8 or Java 8. In some cultures, the number 8 is a number associated with good fortune. Unfortunately, it's just Microsoft's and Java's bad luck to be stupid enough to name a crap product using the number 8. Both products were born on the banqueting table and both products are worthy of being dumped overboard down the toilet.
I'll steer clear of both like I do avoiding dogs poo on the pavement.
Jave 8? Windows 8? Thanks, but no thanks.
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
|
|
|
|
|
> A comprehensive list of exploits will be available sometime after you deploy...
...and this bit of snark has what relevance for anyone reading the article?
|
|
|
|
|
Entertainment value; just like the bit of snark that comes with every other article send out in The Insider.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Right, well this particular one is a partisan straw-man. When was the last time you embedded ActiveX managed code in your page? Probably never--I haven't. It's not as if the ability to run .net code on the client ships with most browsers by default as core functionality. And if such a feature were offered:
- The list of 'sploits would be a thousand miles long, and definitely not available before release (as if such an expectation were even reasonable or made sense);
- Everyone would turn it off;
- It would not count as a strike against the .net platform, but rather against the sandboxing policy in the browser.
I can't wait til HTML5 hits critical mass. Let's see how well the security issues around this are managed by M$. I'm betting on Not Well.
Anyway, even snarky comments should make sense!
Best,
Forty
|
|
|
|
|
The snarky comment made perfect sense to me.
Like it or not of late Java has become known for exploits. Whether it is fair, and whether other systems will have as many problems (HTML5) is not the point. I uninstalled the Java runtime from my home machine. If .NET came with the abiltiy to run client side and had as little use to me and as many problems I might remove that too. Also, if a diet of burgers and beer didn't make me fat I'd be a model.
Until they fix their code and then their PR problem: Java == exploits.
|
|
|
|
|
The Java browser plug-in may be exploitable, but not so much "Java" itself. I understand, of course, that the label "Java" gets applied to a bunch of qualitatively different things. But using the label to cloud and misrepresent matters to users is irresponsible and unethical.
No one likes applets, not even Java people. But almost no one deploys them anyway. The Java platform itself (the back-end: language, JVM, appserver--which, btw, routinely runs on much more secure OSes than the IIS-standard Windows) is less exploitable than the Microsoft equivalent combination (.NET runtime, IIS+Windows OS), and it's this (either intentional or ignorant) implicit false comparison of applets (a marginal use of Java) with _anything_else_ that's incorrect.
Best,
Forty
|
|
|
|
|
That's true. In the last year, the .NET browser plugin has had just as many security holes as the Java plugin, but they weren't actively exploited, so they didn't get the same bad press
|
|
|
|