From what I've read on the whatwg site, this seems like an excellent effort that answers a large portion of the issues I have with web-app development. I'm trying to think of cases it might not cover.
One thing that springs to mind is more complex widgets, such as calenders, include/exclude selectors (two multi-select columns with arrows to move selected items) and that sort of thing. Essentially the type of widgets that are being built in some of the open-source implementations of Java Server Faces.
Anyway, I'll re-read the specs and see if I've anything useful to add:)
Not true. There are a lot of cases, specifically with web-based apps where you can dictate the browser. Whether it's for administrative access to something like a content management system for a portal site, or intranet applications, specifying that a specific browser is used (after agreeing with the client obviously) can be a practical option.
Worked fine for me. Come on, a couple of interface decisions you dislike are hardly a damning indictment.
"very instable, pita to develop (Hellish C++ API)"
Was solid for me. Are you sure you don't mean that a some of the apps were unstable? Perhaps that's linked to people trying to port code that just wasn't deisgned for the level of threading that BeOS used.
"Fast, but mostly useless, with a whole 'unfinished feel' (God, how much that terminal application sucked)"
I completely disagree about the feel. Sure it was somewhat unfinished, but what was done was superb. For a desktop OS it was untouched in terms of responsiveness and simnplicity.
"Hint: I ran NeXTStep at the same time. *This* was an elegant piece of software."
It didn't. The difference was the BeOS 5 PE could be launched from an icon on your desktop and booted in virtually no time at all (~15 seconds including hardware detection?). BeOS *was* being distributed with Windows PCs, unlike linux, which was pretty rough round the edges then. BeOS had all the ease of a user-centric destkop OS, and could be easily bundled on the same PC. MS didn't like that at all and killed it dead.
The Slashdot story is misleading though. It implies that a special case is made for these two companies, and that the tool ignores them. What is actually the case is that the two companies 'products' are in the adware category (along with others) which isn't enabled for filtering by default.
It's not quite the same as the system refusing to remove them, they're just in the category that isn't removed by default.
The Java APIs are technically open source though, anyone can look at the source. They just have particularly nasty licenses attached so that having the source open is pretty much useless.
best place imho is http://www.gemm.com, it's a directory of indy stores, with all their stock listed, so you can do a search and it rifles through hundreds of shops for you:)
also hard to find records http://www.htfr.com/
i've just started a breaks tune with a slightly oldschool flavour, bit rough round the edges, especially the break, but i think i'll pimp it anyway;)
Hardcore as a genre is primarily breakbeat, what was generally called 'rave' in the UK, from about 90/91 to 93/94 (where it started to get silly fast, lose the breakbeats and become more like gabba). Hardcore tracks were often recorded at relatively sedate speeds, around 120-130 bpm, but typically played back at +6 or more.
Examples include, anything on XL around that time, The Prodigy's 'Experience' album (definitely the more commercial end, but some of the singles owned), We are ie, Lord of the Null lines, Sweet Harmony, Suburban Bass recordings, um, my brain defeats me just now, but basically it was the main UK sound for a few years, and it was Jungle came from, before it became its weak cousin drum and bass.
Perhaps, but they are generally objective with their self analysis anyway, so there's no reason to believe that this was a special case.
Anyway, that whole 'scandal' was about one bit of reporting, which was generally seen to be fairly accurate anyway (where are the WMDs?)
The main reason it was blown up so much was because the commercial broadcasting organisations hate the BBC, especially Murdoch ('half' the UK press, Sky TV in the UK, Fox in the states).
Slashdot Mirror
php is fast has a superb set of built in functionality and very flexible, and with php5 has pretty good OO support.
:)
Sure you're not just prejudiced?
hampsterdance.com
:)
hasn't that been outlawed yet?
Blimey... I had no idea. Luckily it's not really my job to know, but still...
The fact that w3c.org is doing this too suggests that there's something quite seriously wrong here. How have we ended up in this situation?
It's a shame that the w3c XHTML validator doesn't seem to pick up on this... Does it?
From what I've read on the whatwg site, this seems like an excellent effort that answers a large portion of the issues I have with web-app development. I'm trying to think of cases it might not cover.
:)
One thing that springs to mind is more complex widgets, such as calenders, include/exclude selectors (two multi-select columns with arrows to move selected items) and that sort of thing. Essentially the type of widgets that are being built in some of the open-source implementations of Java Server Faces.
Anyway, I'll re-read the specs and see if I've anything useful to add
Not true. There are a lot of cases, specifically with web-based apps where you can dictate the browser. Whether it's for administrative access to something like a content management system for a portal site, or intranet applications, specifying that a specific browser is used (after agreeing with the client obviously) can be a practical option.
Rox Desktop / Filer (GTK) does this for Linux, and the filer app (sort of Nautilus replacement) is blindingly fast too.
Scroll down to "Applications are directories"
"Come on, window bar too small"
Oh no!
"Come on, window bar too small"
Worked fine for me. Come on, a couple of interface decisions you dislike are hardly a damning indictment.
"very instable, pita to develop (Hellish C++ API)"
Was solid for me. Are you sure you don't mean that a some of the apps were unstable? Perhaps that's linked to people trying to port code that just wasn't deisgned for the level of threading that BeOS used.
"Fast, but mostly useless, with a whole 'unfinished feel' (God, how much that terminal application sucked)"
I completely disagree about the feel. Sure it was somewhat unfinished, but what was done was superb. For a desktop OS it was untouched in terms of responsiveness and simnplicity.
"Hint: I ran NeXTStep at the same time. *This* was an elegant piece of software."
Ah.. Zealot much?
Most people I know who've used BeOS for any period of time are the same.
It was so elegant.
The (unfortuately unreleased as it was near the end of BeOS' life) OpenGL kit outperformed Linux by about 40%, and Windows by about 50% iirc.
It didn't. The difference was the BeOS 5 PE could be launched from an icon on your desktop and booted in virtually no time at all (~15 seconds including hardware detection?). BeOS *was* being distributed with Windows PCs, unlike linux, which was pretty rough round the edges then. BeOS had all the ease of a user-centric destkop OS, and could be easily bundled on the same PC. MS didn't like that at all and killed it dead.
Ah, I think you're a bit behind on Java.
;)
It's mostly used for large scale applications, particularly ones that need to scale up and out, or are network intensive, or mobile applications.
Applets were a practical joke, didn't you hear?
"looks awesome"
Yeah I'm pretty amazed by the screens I've seen. It's the first game I've seen with depth of field effects, very impressive.
The Slashdot story is misleading though. It implies that a special case is made for these two companies, and that the tool ignores them. What is actually the case is that the two companies 'products' are in the adware category (along with others) which isn't enabled for filtering by default.
It's not quite the same as the system refusing to remove them, they're just in the category that isn't removed by default.
The Java APIs are technically open source though, anyone can look at the source. They just have particularly nasty licenses attached so that having the source open is pretty much useless.
RTFA. They're saying 'open source like Java'.
Hmm, very useful...
Yes thanks, it happened to me, and I fixed it.
oh well of course! it works for you!
it must be fine then!
best place imho is http://www.gemm.com, it's a directory of indy stores, with all their stock listed, so you can do a search and it rifles through hundreds of shops for you :)
;)
3
also hard to find records http://www.htfr.com/
i've just started a breaks tune with a slightly oldschool flavour, bit rough round the edges, especially the break, but i think i'll pimp it anyway
http://slight.overtops.org/mp3/wuuuaaargh-04.mp
Hardcore as a genre is primarily breakbeat, what was generally called 'rave' in the UK, from about 90/91 to 93/94 (where it started to get silly fast, lose the breakbeats and become more like gabba).
Hardcore tracks were often recorded at relatively sedate speeds, around 120-130 bpm, but typically played back at +6 or more.
Examples include, anything on XL around that time, The Prodigy's 'Experience' album (definitely the more commercial end, but some of the singles owned), We are ie, Lord of the Null lines, Sweet Harmony, Suburban Bass recordings, um, my brain defeats me just now, but basically it was the main UK sound for a few years, and it was Jungle came from, before it became its weak cousin drum and bass.
Perhaps, but they are generally objective with their self analysis anyway, so there's no reason to believe that this was a special case.
Anyway, that whole 'scandal' was about one bit of reporting, which was generally seen to be fairly accurate anyway (where are the WMDs?)
The main reason it was blown up so much was because the commercial broadcasting organisations hate the BBC, especially Murdoch ('half' the UK press, Sky TV in the UK, Fox in the states).
The MS v3 optical does 3000 samples a second, haven't found anything that beats it yet. Not sure if you can still get them, but I'd swear by mine.
;)
Works fine under Linux
Ah, thanks for the tip, I'll see if I can get that windows disk mounted and have a peek.
I didn't swap the disks round, I changed the references in menu.1st to point at the opposite disk to the one's they'd been set up with.
*Then* it worked.