Haven't you noticed how every cross-platform C/C++ library starts out with pages of pages of "MY_LIBRARY_INT32" and "MY_LIBRARY_EXPORT" and other redefinitions of "standard" types, keywords, and functions? That's because C is a badly designed language where the behaviour and/or availability of even basic language keywords like "int" is a crap shoot that depends on the compiler and the target processor type
Well, duh. That's the entire point of C. You're complaining that it's a language close to the metal.
Still, since C99 there are special integer types available that define exactly how large they are and if they're unsigned or not. Yes, they are widely available. It's been over 10 years since their introduction.
Meanwhile, this Java code will work on all platforms, processors, and compilers, forever and ever:
At least until Java decides to deprecate parts of its standard library. Java code written during the 90s no longer works. So much for "write once".
I got the input parameters correct on the first try because I used a WINAPI tutorial and Borland's WINAPI documentation. So I guess the lesson is that MSDN's documentation sucks?
You ask me for clarification but post as Anonymous Coward? Okay...
define "long time" please.
Hours, sometimes even a day.
As for breaking tabbed browsing and bad javascript, what the hell browser are you using, because I've never had any of those issues in firefox or IE or chrome, and on my phone, never had those issues in the android browser.
Try middle-clicking on messages in your inbox sometime, or on some button. It just reloads the inbox, if memory serves.
As for bad JavaScript, it's mostly related to dumb user agent sniffing that randomly breaks functionality even if you spoof your user agent string. Other than that, have you tried looking at it? It's garbage.
And yes, I have used Hotmail in this decade. If I didn't, I wouldn't have known about the current problems that weren't there back when first registered a Hotmail account. It had none of these issues back then. I actually liked Hotmail Classic quite a bit back when they first introduced the new interface. It was slick and fast. Then they forced me to use the AJAXy crap.
Oh, and Windows native C++ development is horrible. Just look at how you're supposed to display the standard "open files" dialog and get the selected file names.
I have in the past. What's horrible about it? Seemed pretty easy to me.
I'm one of two developers on a custom remote debugger for reverse engineering and hacking Wii games, so my experience is generalized beyond just x86. I can look through PowerPC assembly and see the game iterating over an array of enemies, evaluating whether they have any damage pending, stuff like that.
Sounds awesome. This gives me hope for an eventual hack of Mega Man 9 and Mega Man 10 that adds progressive scan support to them. (Damn you, Capcom!)
Those components that are shared with Internet Explorer are the IE core. It's part of it. They just jammed it into the system and made everything depend on it.
For my money, IE has been a tightly integrated component of Windows all along, and naturally so, since you can hardly expect any modern OS vendor to ship an OS without an HTML engine.
I don't agree. You can hardly expect any modern OS vendor to ship an OS without a web browser, but a HTML engine? It should be removable together with the actual web browser. If an application wants to show a web page it can just call the default web browser like applications have been doing for over a decade.
Because the Catch-22 is that if you just say "no IE," naturally there's no way to download anything else! (Which is where the whole thing starts to get a little silly, if you ask me.)
Bullshit. OEMs can pre-install web browsers, and there are other ways to get a web browser on the computer that don't involve an Internet connection. It's not like you need a web browser to download something over an Internet connection either.
Re:What is my overriding reason to migrate off XP?
on
10 Years of Windows XP
·
· Score: 1
nobody in their right mind, except for the people who designed those can and bottle recycling kiosks, still runs Windows 98.
There are people out there who still run Windows 98. I was one of them until I needed to buy a new hard drive for the computer that dual-booted it with Windows XP. I run Windows 95 on my main computer. Works great and does what I need.
At 10 years old, XP is like a Linux system stuck on Kernel 2.2, KDE 2.2, Xfree86 4.1, and GTK 1.2. The fact that such an old configuration is still supported to any extent and remains thoroughly tested by software developers is nuts. Like with web devs and IE6, most probably can't wait to drop it.
No, what's nuts is this perpetual upgrading cycle that requires us to buy a new OS along with (a) new computer (parts) so we can run a supported OS configuration.
You know why web developers (like me) loathe IE6? Three reasons:
Because its web standards support is sorely lacking.
Lots of rendering bugs.
The web evolves, which spawns new requirements and new web standards to accomodate them.
It's a vastly different situation than a home computer. It has to work well and fulfill my requirements. If my OS meets my requirements, I shouldn't be forced to change it because some software company decided that it needs to release a new version and stop supporting the current one.
And no, Linux isn't totally immune from this, as Linux 2.6 dropped support for a lot of older hardware.
It's amazing what you can do with 256 MB of RAM when you don't have an OS that eats all of it for breakfast. Hell, my primary computer has 'only' 160 MB of RAM, and it's enough for most of my computing needs.
how do older browsers react to doctypes developed after the browser was created?
The WHATWG made sure to choose a DOCTYPE for HTML5 that every web browser deems sufficient to turn on standards compliant mode.
As for the new HTML elements, it depends on the browser. Mozilla browsers treat them like every other element, except they get no default styling (which makes sense). Internet Explorer ignores all elements that it doesn't recognise until you make some of them with JavaScript's createElement DOM method. I have no idea what older WebKit-based ones and older Opera versions do.
There is no law written. Yet. But as the entire point of the xxx TLD is to get all porn moved there, it has been argued that it won't take long for one to be written.
No more so than people who say "we've already gone through the arguments" as if simply saying that was sufficient to prove their point.
Every other article had comments explaining why it was a bad idea, so I thought it'd be silly for me to repeat that as people would know by now.
I followed that road and now I'm stuck because game developers refuse to share any knowledge on intermediate difficulty topics. The only 'help' I get is to sling shit at the wall until something sticks.
I mean, it's full of objects with derivation and virtual functions, and structs on which constructors and destructors have to be called for everything to remain in one peice. Seems odd not to use a language which is every bit as efficient, has a familiar syntax and yet does a large number of common tasks automatically and without errors.
The special treatment that C++ gives to constructors and destructors makes things harder, though. They don't return any value. If the constructor fails your only option is to throw an exception. But C++ exceptions make code execution slower. Another alternative is to check the object through a method after construction, which a lot of STL objects do, but that's kind of messy.
Don't get me wrong; I program in C++. But this is one of the dilemmas that I've faced and researched, and I still don't know what to do about it.
Slashdot Mirror
Well, duh. That's the entire point of C. You're complaining that it's a language close to the metal.
Still, since C99 there are special integer types available that define exactly how large they are and if they're unsigned or not. Yes, they are widely available. It's been over 10 years since their introduction.
At least until Java decides to deprecate parts of its standard library. Java code written during the 90s no longer works. So much for "write once".
I got the input parameters correct on the first try because I used a WINAPI tutorial and Borland's WINAPI documentation. So I guess the lesson is that MSDN's documentation sucks?
Okay, but you dodged my actual question. That doesn't explain your first example: opening a file open dialog and getting the selected files.
By the way, Borland's WINAPI documentation is better than Microsoft's.
Try hours, sometimes even a day for a message to arrive in my inbox.
You ask me for clarification but post as Anonymous Coward? Okay...
Hours, sometimes even a day.
Try middle-clicking on messages in your inbox sometime, or on some button. It just reloads the inbox, if memory serves.
As for bad JavaScript, it's mostly related to dumb user agent sniffing that randomly breaks functionality even if you spoof your user agent string. Other than that, have you tried looking at it? It's garbage.
And yes, I have used Hotmail in this decade. If I didn't, I wouldn't have known about the current problems that weren't there back when first registered a Hotmail account. It had none of these issues back then. I actually liked Hotmail Classic quite a bit back when they first introduced the new interface. It was slick and fast. Then they forced me to use the AJAXy crap.
No, it's not. It's just a mark-up language. There is nothing graphical about it. You should look at something like XUL instead.
I have in the past. What's horrible about it? Seemed pretty easy to me.
Sounds awesome. This gives me hope for an eventual hack of Mega Man 9 and Mega Man 10 that adds progressive scan support to them. (Damn you, Capcom!)
It still does dumb user agent sniffing and throws tons of bad JavaScript at you. Its AJAXy interface breaks tabbed browsing.
As for the service itself, e-mail messages that aren't sent using Hotmail take a long time to arrive.
Quite good my ass.
You mean it's easier to create web pages for IE's buggy rendering engine and JavaScript engine?
Firefox is already multi-threaded. What you're talking about is multi-process.
Those components that are shared with Internet Explorer are the IE core. It's part of it. They just jammed it into the system and made everything depend on it.
I don't agree. You can hardly expect any modern OS vendor to ship an OS without a web browser, but a HTML engine? It should be removable together with the actual web browser. If an application wants to show a web page it can just call the default web browser like applications have been doing for over a decade.
Bullshit. OEMs can pre-install web browsers, and there are other ways to get a web browser on the computer that don't involve an Internet connection. It's not like you need a web browser to download something over an Internet connection either.
There are people out there who still run Windows 98. I was one of them until I needed to buy a new hard drive for the computer that dual-booted it with Windows XP. I run Windows 95 on my main computer. Works great and does what I need.
No, what's nuts is this perpetual upgrading cycle that requires us to buy a new OS along with (a) new computer (parts) so we can run a supported OS configuration.
You know why web developers (like me) loathe IE6? Three reasons:
It's a vastly different situation than a home computer. It has to work well and fulfill my requirements. If my OS meets my requirements, I shouldn't be forced to change it because some software company decided that it needs to release a new version and stop supporting the current one.
And no, Linux isn't totally immune from this, as Linux 2.6 dropped support for a lot of older hardware.
Unlike laptops, PCs (desktops) can easily be assembled from parts you buy yourself, without a bundled OS.
It's amazing what you can do with 256 MB of RAM when you don't have an OS that eats all of it for breakfast. Hell, my primary computer has 'only' 160 MB of RAM, and it's enough for most of my computing needs.
That sounds more like Slashdot, which I'm sure is the joke. :)
The WHATWG made sure to choose a DOCTYPE for HTML5 that every web browser deems sufficient to turn on standards compliant mode.
As for the new HTML elements, it depends on the browser. Mozilla browsers treat them like every other element, except they get no default styling (which makes sense). Internet Explorer ignores all elements that it doesn't recognise until you make some of them with JavaScript's createElement DOM method. I have no idea what older WebKit-based ones and older Opera versions do.
There is no law written. Yet. But as the entire point of the xxx TLD is to get all porn moved there, it has been argued that it won't take long for one to be written.
Every other article had comments explaining why it was a bad idea, so I thought it'd be silly for me to repeat that as people would know by now.
I followed that road and now I'm stuck because game developers refuse to share any knowledge on intermediate difficulty topics. The only 'help' I get is to sling shit at the wall until something sticks.
I refuse to reinvent the wheel.
Those are quite bad and biased reasons. So it's basically C elitism. Let's all ignore that C has problems of its own.
The special treatment that C++ gives to constructors and destructors makes things harder, though. They don't return any value. If the constructor fails your only option is to throw an exception. But C++ exceptions make code execution slower. Another alternative is to check the object through a method after construction, which a lot of STL objects do, but that's kind of messy.
Don't get me wrong; I program in C++. But this is one of the dilemmas that I've faced and researched, and I still don't know what to do about it.
The whole point of the .xxx TLD is that all porn sites will move to it under pressure of the law.
Now you're just being an ass. Just search Slashdot for similar stories if it interests you. Honestly, it's been mentioned pretty much every time.