|
|
Kent Sharkey wrote: who doesn't want to write stuff like this in their JavaScript?
Me.
However I have never for one moment in my life actually wanted to write anything in JavaScript, especially not when I was writing JavaScript.
Anyone who doesn't know the difference between interpreted language and language open to interpretation shouldn't be writing a language or an interpretter and if they do noone should attempt to use it for anything other than unflattering comparisons with Malbolge.
"The secret of happiness is freedom, and the secret of freedom, courage."
Thucydides (B.C. 460-400)
|
|
|
|
|
In this installment we talk to Chris Pardo, a Senior Product Manager at Dun and Bradstreet. Learn about how the Dun & Bradstreet rapid-prototype team helps customers use D&B APIs and data services in their apps. Plus: Chris is moderating the D&B Developer Challenge (http://dnbdirectapps.com/microsoft/).
|
|
|
|
|
The C language does not describe an actual computer. It describes a theoretical one. On this theoretical computer, it must be possible to do certain things, like generate the address of one item past the end of an array, and that address must compare greater than the address of any member of the array. But how the C language implementation chooses to map these theoretical operations to actual operations is at the discretion of the C language implementation. And does this mean it's impossible to write a conforming C compiler for MS-DOS?
|
|
|
|
|
In effect, the optimizing allocator has added a performance breakpoint: The program's performance is sharply different for sizes larger than the threshold than it is for smaller sizes. My colleague argued that such performance breakpoints are evil, because when people who use the code learn about the breakpoints, they will change their own behavior to compensate for the breakpoints. Once they do that, the people who use their code will change their own behavior, and so on. The original performance breakpoint may well result in ripple effects that complicate entire systems. As a result, my colleague argued that it is more important to design systems so that their performance changes smoothly with input size than it is to make them run very quickly on particular input sizes. A necessary evil, and a philosophical conundrum.
|
|
|
|
|
Sometimes, the state of your website’s security can be affected by resources and services outside your control. The topic of today? Browser extensions. If you didn’t generate it, assume it’s malicious.
|
|
|
|
|
Programming is hard. Don't ever feel bad because you aren't as good at 'just googling it' as the person next to you. Don't ever let hackathon snobs talk you out of creating the next Twitter for cats or Yelp for public washrooms. Even the dumbest ideas (like trying to make animated polygons disappear and reappear) will help you improve as a programmer. Learning to program is largely about learning to learn--and the best way to learn is to do. At the end of the day, being a competent programmar isn't about how many hackathons you win or how many novel ideas you can come up with--it's about execution, attention to detail, and relentless dedication and passion for building and breaking. If you ever feel self-conscious about your code, I'll allow a laugh at my expense.
|
|
|
|
|
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.
|
|
|
|