Not to mention, it's just as likely as "The president will be delivered at the drop-off location at precisely 0400 hours. He then will be transported to a secure, hidden facility."
Anyone with VLC could have watched the keynote. Apple was using standard RFC-standard HTTP video streaming. Microsoft hasn't implemented it on Windows yet — what do you want them to do?
As a person who does virtually all my personal transportation by bicycle, I am going to request that you read the goddamn book of traffic laws for your state. In every state in this country and in virtually the rest of the world, bicycles are vehicles and have exactly as much a right to the road as cars, motorcycles, scooters, or any other vehicle. In fact, most cities explicitly prohibit bicycles from riding on the sidewalks.
I have to have this same conversation with every damn person who honks at me for riding a bicycle on the road. Non-motorized pathways, including separate bike paths or sidewalks, are actually more dangerous than cycling on the road — various studies peg the number from anywhere between two to seven times as dangerous. And I can say from my own personal experience that of the 3,700 miles I have logged, fewer than 10 of them in aggregate have been on sidewalks, and I've been hit by a car while on the sidewalk.
To sum, cyclists are not required by law to ride in bike lanes, on bike paths, or on the sidewalks, and in fact that's usually the most dangerous place for them to possibly be. Sidewalks and bike paths are dangerous because drivers aren't looking for objects traveling 20mph off the road, and it's incredibly easy to be hit while crossing intersections, driveways, or parking lot entrances. Bike lanes are often more dangerous because they are commonly located in the "door zone" for parallel-parked cars, putting you right in the way of absent-minded drivers flinging their doors open directly in front of you. So share the damn road already, and be grateful that someone else in the world is making the roads safer for you at a greatly increased risk to their own bodies while reducing overall traffic congestion (cycling reduces usage of main thoroughfares and distributes the load to less-trafficked side streets)
The kind of bugs you catch with a compiler are the kind of bugs that rarely if ever actually occur in practice in interpreted languages. In all my years of coding in Perl, Ruby, and Javascript, I have never encountered a single bug where somebody inserted a string into an array meant for integers, or one where someone tries to compare a float to an array. Time spent painstakingly documenting shit to the compiler is time you could spend actually writing tests that exercise your code, revealing the bugs that _really_ matter.
Both self-taught programmers and school-taught programmers have gaps. I feel like I got pretty good exposure to both scenarios, since I was self-taught but did go to college, where I had some of those gaps filled in (and also took plenty of courses where I learned precious little).
Some things that self-taught programmers often lack are,
an intuitive notion of algorithm running-time (i.e., big-O)
design patterns, and how to create new ones.
There's others (compiler theory, AI, whatever), but in practical software development those are the two that come up most often. But I find that self-taught programmers are often better at what they do than school-educated ones, because they are sensitive to the gaps they have, and they know how to learn things on their own.
School-taught programmers on the other hand have far, far more gaps in my experience. They often lack
understanding of and experience with version control
the ability to write software for others to use or maintain
the ability to teach themselves new languages or tools.
In my opinion the main problems with current Computer Science curricula are that the professors themselves are heavily isolated from real-world application development. Courses on version control (especially newer tools like git or mercurial as opposed to CVS) are virtually nonexistent. Courses that teach students how to structure code for others to use (ex., writing code as a library for others to link against) don't exist. Because Computer Science courses are isolated from real-world needs like maintenance and working with others, the only criteria students' code is judged on is whether or not it produces correct output.
Students learn one or two languages, but virtually always languages that share roughly the same syntax (e.g., C++ and Java). Very little time is spent on highly-productive scripting languages like Ruby, JavaScript, or Python. And students are never taught to adapt their solutions to the strengths of different languages. If they learn Java first, every program they write will try to solve it the "Java way". Not to pick on Java — the point is simply that nobody is taught to identify and use the strengths of languages, or learn their common idioms, so they just write everything like it's their Language of Choice.
Also, your original argument is that you lose compatibility with "many applications, the majority of which are made for Windows", which is a bit like saying picking a Toyota loses you compatibility with Ford parts.
Third-party Mac software is, in my experience, generally (an important distinction there) far better designed and well-written than third-party Windows software. Mac developers, by and large, care about their craft, and care about their platform. The vast majority of Windows developers are clueless, incompetent, or don't care. (Note that there are still many, many good Windows applications and Windows developers out there; I'm simply stating that proportionally speaking, Windows developers are incompetent tools).
Your argument was that you lose compatibility with applications. I called bullshit, and you're still wrong on that.
But for your current point, practically speaking, the total cost is $80 for a VMWare Fusion license. Because anyone switching from a Windows computer will already have a license for Windows, and can even bundle up their existing box and run their existing software in a VM by bundling their box over WiFi or with a spare Ethernet cable.
Don't buy a Mac if you intend to play games... unless you are techy enough to dual-boot your Mac.
This isn't 2004 any more. Plenty of developers release native ports of games for the Mac. And with VMWare Fusion 3, you can play any DirectX 9 Shader Model 3.0 game directly in a Windows box running on your desktop.
And lose compatibility with many applications, the majority of which are made for Windows. Sure, Adobe suite and some of Microsoft Office are ported, but some businesses depend on third-party apps that require Microsoft Access.
Yes, because VMWare Fusion hasn't been out for ages now. I do web development on a Mac, and I keep an instance of Ubuntu and an instance of Windows running on my previous-generation Mac Mini running at all times to test performance and rendering in different browsers.
Seconded.
Although at the time I was in college, I ran Linux, and couldn't use Scientific Notebook. So I just learned LaTeX instead. Got damn fast at it, too, copying notes in real-time. But my experiences with Scientific Notebook were absolutely enjoyable.
Look. You've practically admitted (both explicitly, and implicitly by your clear naivete when it comes to this topic) that you've been exposed to hammers as your only problem-solving tool. Just acknowledge that you can't conceive of how your hammer isn't the best tool for solving screw-shaped problems and expand your damned horizons already.
The twitter folks are pretty smart. Given the size of the traffic they have to handle, and their complete and intentional lack of blaming Rails at every step of the way, do you really think it's Rails, or other parts of their infrastructure?
Actually, the use of method_missing is discouraged because it's slow and difficult to extend when multiple features end up needing it. Much better is to dynamically do define_method / alias_method / etc.
Excuse me? OSX windows don't have borders. And since the menu bar is fixed to the top of the screen, the top bar is thin -- about 2/3 the height of Windows, at rough guess. When was the last time you used a Mac?
I realize you're joking, but relativity doesn't let you get away with that. Being in orbit, we're experiencing detectable acceleration, meaning we're not "sitting still", regardless the perspective.
Slashdot Mirror
Not to mention, it's just as likely as "The president will be delivered at the drop-off location at precisely 0400 hours. He then will be transported to a secure, hidden facility."
Anyone with VLC could have watched the keynote. Apple was using standard RFC-standard HTTP video streaming. Microsoft hasn't implemented it on Windows yet — what do you want them to do?
As a person who does virtually all my personal transportation by bicycle, I am going to request that you read the goddamn book of traffic laws for your state. In every state in this country and in virtually the rest of the world, bicycles are vehicles and have exactly as much a right to the road as cars, motorcycles, scooters, or any other vehicle. In fact, most cities explicitly prohibit bicycles from riding on the sidewalks.
I have to have this same conversation with every damn person who honks at me for riding a bicycle on the road. Non-motorized pathways, including separate bike paths or sidewalks, are actually more dangerous than cycling on the road — various studies peg the number from anywhere between two to seven times as dangerous. And I can say from my own personal experience that of the 3,700 miles I have logged, fewer than 10 of them in aggregate have been on sidewalks, and I've been hit by a car while on the sidewalk.
To sum, cyclists are not required by law to ride in bike lanes, on bike paths, or on the sidewalks, and in fact that's usually the most dangerous place for them to possibly be. Sidewalks and bike paths are dangerous because drivers aren't looking for objects traveling 20mph off the road, and it's incredibly easy to be hit while crossing intersections, driveways, or parking lot entrances. Bike lanes are often more dangerous because they are commonly located in the "door zone" for parallel-parked cars, putting you right in the way of absent-minded drivers flinging their doors open directly in front of you. So share the damn road already, and be grateful that someone else in the world is making the roads safer for you at a greatly increased risk to their own bodies while reducing overall traffic congestion (cycling reduces usage of main thoroughfares and distributes the load to less-trafficked side streets)
You're welcome.
Love my Brooks. I recommend it to everyone, and won't ride anything but it.
No, it is not.
a = x if foo
The kind of bugs you catch with a compiler are the kind of bugs that rarely if ever actually occur in practice in interpreted languages. In all my years of coding in Perl, Ruby, and Javascript, I have never encountered a single bug where somebody inserted a string into an array meant for integers, or one where someone tries to compare a float to an array. Time spent painstakingly documenting shit to the compiler is time you could spend actually writing tests that exercise your code, revealing the bugs that _really_ matter.
This mentality is precisely why Windows Mobile has been a complete and utter failure.
Both self-taught programmers and school-taught programmers have gaps. I feel like I got pretty good exposure to both scenarios, since I was self-taught but did go to college, where I had some of those gaps filled in (and also took plenty of courses where I learned precious little).
Some things that self-taught programmers often lack are,
There's others (compiler theory, AI, whatever), but in practical software development those are the two that come up most often. But I find that self-taught programmers are often better at what they do than school-educated ones, because they are sensitive to the gaps they have, and they know how to learn things on their own.
School-taught programmers on the other hand have far, far more gaps in my experience. They often lack
In my opinion the main problems with current Computer Science curricula are that the professors themselves are heavily isolated from real-world application development. Courses on version control (especially newer tools like git or mercurial as opposed to CVS) are virtually nonexistent. Courses that teach students how to structure code for others to use (ex., writing code as a library for others to link against) don't exist. Because Computer Science courses are isolated from real-world needs like maintenance and working with others, the only criteria students' code is judged on is whether or not it produces correct output.
Students learn one or two languages, but virtually always languages that share roughly the same syntax (e.g., C++ and Java). Very little time is spent on highly-productive scripting languages like Ruby, JavaScript, or Python. And students are never taught to adapt their solutions to the strengths of different languages. If they learn Java first, every program they write will try to solve it the "Java way". Not to pick on Java — the point is simply that nobody is taught to identify and use the strengths of languages, or learn their common idioms, so they just write everything like it's their Language of Choice.
RAID 0 is for chumps. You get a similar read speed boost from RAID 1, and you don't have the dramatically increased risk of failure.
Also, your original argument is that you lose compatibility with "many applications, the majority of which are made for Windows", which is a bit like saying picking a Toyota loses you compatibility with Ford parts.
Third-party Mac software is, in my experience, generally (an important distinction there) far better designed and well-written than third-party Windows software. Mac developers, by and large, care about their craft, and care about their platform. The vast majority of Windows developers are clueless, incompetent, or don't care. (Note that there are still many, many good Windows applications and Windows developers out there; I'm simply stating that proportionally speaking, Windows developers are incompetent tools).
Your argument was that you lose compatibility with applications. I called bullshit, and you're still wrong on that.
But for your current point, practically speaking, the total cost is $80 for a VMWare Fusion license. Because anyone switching from a Windows computer will already have a license for Windows, and can even bundle up their existing box and run their existing software in a VM by bundling their box over WiFi or with a spare Ethernet cable.
Great, you hate iTunes. So drag it to the Trash and it's gone. Totally.
Find me an uninstall process that simple for anything bundled with your PC.
Don't buy a Mac if you intend to play games... unless you are techy enough to dual-boot your Mac.
This isn't 2004 any more. Plenty of developers release native ports of games for the Mac. And with VMWare Fusion 3, you can play any DirectX 9 Shader Model 3.0 game directly in a Windows box running on your desktop.
Yes, because VMWare Fusion hasn't been out for ages now. I do web development on a Mac, and I keep an instance of Ubuntu and an instance of Windows running on my previous-generation Mac Mini running at all times to test performance and rendering in different browsers.
There's no tradeoff any more whatsoever.
Seconded. Although at the time I was in college, I ran Linux, and couldn't use Scientific Notebook. So I just learned LaTeX instead. Got damn fast at it, too, copying notes in real-time. But my experiences with Scientific Notebook were absolutely enjoyable.
This isn't patent trolling... this takes it to a whole new level. I suggest the term "patent griefing".
A new scientific breakthrough allows law enforcement officials to automatically detect people trying to look suspicious! News at 11...
Likewise, as a programmer, if I had a dollar for every mess caused by J Undergrad Javabot, I could have retired at 30.
Look. You've practically admitted (both explicitly, and implicitly by your clear naivete when it comes to this topic) that you've been exposed to hammers as your only problem-solving tool. Just acknowledge that you can't conceive of how your hammer isn't the best tool for solving screw-shaped problems and expand your damned horizons already.
The twitter folks are pretty smart. Given the size of the traffic they have to handle, and their complete and intentional lack of blaming Rails at every step of the way, do you really think it's Rails, or other parts of their infrastructure?
Actually, the use of method_missing is discouraged because it's slow and difficult to extend when multiple features end up needing it. Much better is to dynamically do define_method / alias_method / etc.
I realize you're joking, but relativity doesn't let you get away with that. Being in orbit, we're experiencing detectable acceleration, meaning we're not "sitting still", regardless the perspective.
Matroska is a container format. Which is not a codec. Go ahead and grep that Wikipedia page for the word "codec" and you'll see what I mean.