Novell doesn't really seem interested in the openSUSE community beyond using them as free testers anyway. Build Service notwithstanding, openSUSE is built by Novell and not by its community. Bugs on the bugzilla can link via dependency to closed internal bugs and then it's just "sorry, that's internal, we'll fix it now sit quietly please".
I think there's some people with hearts in the right place even inside Novell (I'm not just talking about the Czech and German teams) but as an aggregate they don't show much sign on "getting it" where the community model is concerned.
I can't explain it (oh okay, maybe I can) when the database in question contains/. comments and old Jon Katz stories (quite apart from Taco's nicely spelled and eloquent posts), calling it a dump somehow seems appropriate in the more scatological sense of that word...
It's just those boffins at Hubble grumbling. Think about it, do you really think you'll get smileys and flirty leetspeak messages via Hubble? No. And that is why Hubble is so effing cheap.
I'm trying to envision a set of conditions whereby the states "dead" and "not doing anything" are in a one-or-the-other relationship as suggested by the "or" between then. Oh right, zombies! Dead, still pretty busy, therefore satisfying the conditions set forth by your choice of words.
I use sites like YouTube enough that I'd pay to get rid of 15 second ads every video play.
Youtube finally found its (one person) market! Now if you can figure out how to cover a USD 1 billion annual subscription fee, we'll have sorted out the site's revenue model once and for all.
... and I've had to address it. It is possible this might be of interest and relevance; I worked some time in microfinance, and was asked to deliver a capacity building workshop on IT for senior leadership. Managed to make it Creative Commons.:) But a glance at the deck goes a long way to illustrating the kind of fundamental lack of understanding and pragmatism towards enterprise IT which the article refers to.
FWIW, I think one of the key outputs of IT Governance implementation is to stamp out this form of disconnect.
The "1 in 5" statistic is seriously skewed by the avalanche of propositions Taco receives. Yes Taco, we've seen the notches now stop reporting these incidents please.
<pre> [user@laptop pts/4] python Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. Please be aware that this technology has addictive qualities; use with moderation. For more information, speak with your doctor or call 1-800-TOO-MUCH >>> </pre>
The lack of weighty subjects ceased being a problem in the video game industry many years ago, when Tomb Raider's Lara Croft gave us not one but two weighty subjects to consider.
I'm not so sure about the "you do not" bit in the following from your post:
You DO NOT and SHALL NOT ever control other nations laws
WIPO pretty much propagates what the US congress lays down in law. To take the section on Egypt asan example in the Special 301 Report, the country is being egged on to sign on and apply WIPO.
US free trade zones also carry very strict IP enforcement agreements as strings, and yet developing nations still fall over themselves to hop on board with these.
If there is easy access to outlets for banality, two things will happen: 1. The proportion of meaningful protest to Britney Spears wannabes is going to plummet 2. The average person will be more inclined to posting the banal; it is easier 3. Those expressing meaningful ideas will be marginalized and will gravitate to clusters which makes it easier to marginalize them
And that concludes my presentation on why a web for the common joe sucks. Thank you, and please be gentle with the shackles.
Yes. This is, to be more specific, just another example of the phenomenon that people will research anything which will press peoples' buttons. Whether it is valuable research or not. Who gives these people grants?
My cat fetches; will someone give me a grant? I want to find out whether he is a dog.
Re:Obligatory
on
DIY Laptop
·
· Score: -1, Offtopic
Those +1 Funny you're getting? I think it's your sig.
A real hacker(tm) would have made a dumb remark about how leet it could have been according to the daydreams of some fricking moron with a 9xxxxx uid on slashdot sitting eating cheetos in his moms^W grandma's basement with a mediocre report card and a fat fricking belly (it's them cheetos, moron!) and a boner for the neighbor's collie he's afraid to talk about.
Sheesh, when did my little brother's classmates find out about slashdot. How ANNOYING. Goddamit, you link to wikipedia in your personal URL? Have some geocities/blogspot dignity!
Yes, Swedish passwords are weak. We Danes have known this for many years; it is inevitable given that the average number of syllables per word in Swedish is 1.22 (scientific studies have shown it!).
"sigge", a duosyllabic password, is an indication that the user was a member of the upper strata of Swedish society, with Abba and Ace of Base.
(NB: I can handle pissed off Swedes, but not moderators lacking the humor gene)
I work providing MIS technical assistance in microfinance (used to be an open source consultant). I've seen a lot of Visual Basic applications in service of microfinance institutions and I've seen the consequences.
What I've seen has been mainly Access being used as a RAD to develop portfolio management systems, with VBA constituting the language the logic is developed in. Some observations:
1. Such applications when used over the medium to long run invariably become unmaintainable. The business changes, loan products change, organizational structure changes, new needs arise, servers are upgraded, etc. This we all know; there is no such thing as finished software. A VB application has the advantage of getting up and running fast, but as the code changes accumulate over the years, the code becomes unmaintainable; a change here b0rks fifteen things elsewhere and the developer (often one person) eventually gets to the stage where he just says "no, we can't do this". IF you're lucky, he tells you that it's because he needs to reqrite the app. If you're not, he attributes the limitation to the abstract god of technology.
2. The Access/VB development environment is indeed a VRAD (very RAD). You can go from zero to information system in almost no time with almost no resources (the typical scenario of one developer mentioned previously). TH downside is that when you have this few people working on the system, it can be underdocumented. Which means that when your magical one-man development team jets, it's going to be easier to rewrite the application from scratch (and when that crisis comes, it's often rewritten in Access/VBA again, since a system is needed, FAST). Oh my aching bones...
3. Mentioned elsewhere, but these MS products are EOL'ed periodically. No support. No bug fixes. No security fixes. One often overlooked consequence of this is that MS drives the techie labor market towards its current offerings; what this means is that you are not going to expect a VB-based product to last, since a few years down the road the Microsoft marketing machine has changed the paradigm and driven developers towards other technologies, limiting the availability of engineers to feed your monster.
4. When you're developing a system for business usage, you're going to want to have several things which more proefessional toolchains make more readily expose; things which, more likely than not you can accomplish nominally in VB albeit with a lot of workaounds and in many cases not very reliably and sub-optimally. Audit trails, transaction atomicity, multi-user functionality, etc.
I'll post more if I canthink of them. Good to have a reference of VB drawbacks, especially since I see it so often.
My punch cards never stopped working also, so like you I never saw the sense in upgrading.
What is an LCD by the way?
Novell doesn't really seem interested in the openSUSE community beyond using them as free testers anyway. Build Service notwithstanding, openSUSE is built by Novell and not by its community. Bugs on the bugzilla can link via dependency to closed internal bugs and then it's just "sorry, that's internal, we'll fix it now sit quietly please".
I think there's some people with hearts in the right place even inside Novell (I'm not just talking about the Czech and German teams) but as an aggregate they don't show much sign on "getting it" where the community model is concerned.
I can't explain it (oh okay, maybe I can) when the database in question contains /. comments and old Jon Katz stories (quite apart from Taco's nicely spelled and eloquent posts), calling it a dump somehow seems appropriate in the more scatological sense of that word...
It's just those boffins at Hubble grumbling. Think about it, do you really think you'll get smileys and flirty leetspeak messages via Hubble? No. And that is why Hubble is so effing cheap.
I'm trying to envision a set of conditions whereby the states "dead" and "not doing anything" are in a one-or-the-other relationship as suggested by the "or" between then. Oh right, zombies! Dead, still pretty busy, therefore satisfying the conditions set forth by your choice of words.
*phew*
I mean, I can't be the only one who thought this would be an article about the Internet Explorer team at Microsoft?
Youtube finally found its (one person) market! Now if you can figure out how to cover a USD 1 billion annual subscription fee, we'll have sorted out the site's revenue model once and for all.
Is it even possible for an article frontpaging on /. to be less original and more fluffy?
FWIW, I think one of the key outputs of IT Governance implementation is to stamp out this form of disconnect.
I can't be the only person whose speed-reading eyes stumble over themselves every time I see that fellow's family name?
The "1 in 5" statistic is seriously skewed by the avalanche of propositions Taco receives. Yes Taco, we've seen the notches now stop reporting these incidents please.
<pre>
[user@laptop pts/4] python
Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32)
[GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Please be aware that this technology has addictive qualities; use with moderation.
For more information, speak with your doctor or call 1-800-TOO-MUCH
>>>
</pre>
The lack of weighty subjects ceased being a problem in the video game industry many years ago, when Tomb Raider's Lara Croft gave us not one but two weighty subjects to consider.
Their internet is b0rked?
The payphone will never be obsolete so long as we have Superman.
I can't believe the iphone didn't make it. This list is totally bogus.
I'm not so sure about the "you do not" bit in the following from your post:
You DO NOT and SHALL NOT ever control other nations laws
WIPO pretty much propagates what the US congress lays down in law. To take the section on Egypt asan example in the Special 301 Report, the country is being egged on to sign on and apply WIPO.
US free trade zones also carry very strict IP enforcement agreements as strings, and yet developing nations still fall over themselves to hop on board with these.
Panem et circenses.
If there is easy access to outlets for banality, two things will happen:
1. The proportion of meaningful protest to Britney Spears wannabes is going to plummet
2. The average person will be more inclined to posting the banal; it is easier
3. Those expressing meaningful ideas will be marginalized and will gravitate to clusters which makes it easier to marginalize them
And that concludes my presentation on why a web for the common joe sucks. Thank you, and please be gentle with the shackles.
But is this finding just a gender stereotype?
Yes. This is, to be more specific, just another example of the phenomenon that people will research anything which will press peoples' buttons. Whether it is valuable research or not. Who gives these people grants?
My cat fetches; will someone give me a grant? I want to find out whether he is a dog.
Those +1 Funny you're getting? I think it's your sig.
You do realise that refereeing for journals is often unpaid work work right?
Paid by the word, are we we?
A real hacker(tm) would have made a dumb remark about how leet it could have been according to the daydreams of some fricking moron with a 9xxxxx uid on slashdot sitting eating cheetos in his moms^W grandma's basement with a mediocre report card and a fat fricking belly (it's them cheetos, moron!) and a boner for the neighbor's collie he's afraid to talk about.
Sheesh, when did my little brother's classmates find out about slashdot. How ANNOYING. Goddamit, you link to wikipedia in your personal URL? Have some geocities/blogspot dignity!
Yes, Swedish passwords are weak. We Danes have known this for many years; it is inevitable given that the average number of syllables per word in Swedish is 1.22 (scientific studies have shown it!).
"sigge", a duosyllabic password, is an indication that the user was a member of the upper strata of Swedish society, with Abba and Ace of Base.
(NB: I can handle pissed off Swedes, but not moderators lacking the humor gene)
For a second, I thought this had something to do with the proper disposal of movies like Battlefield Earth...
I work providing MIS technical assistance in microfinance (used to be an open source consultant). I've seen a lot of Visual Basic applications in service of microfinance institutions and I've seen the consequences.
What I've seen has been mainly Access being used as a RAD to develop portfolio management systems, with VBA constituting the language the logic is developed in. Some observations:
1. Such applications when used over the medium to long run invariably become unmaintainable. The business changes, loan products change, organizational structure changes, new needs arise, servers are upgraded, etc. This we all know; there is no such thing as finished software. A VB application has the advantage of getting up and running fast, but as the code changes accumulate over the years, the code becomes unmaintainable; a change here b0rks fifteen things elsewhere and the developer (often one person) eventually gets to the stage where he just says "no, we can't do this". IF you're lucky, he tells you that it's because he needs to reqrite the app. If you're not, he attributes the limitation to the abstract god of technology.
2. The Access/VB development environment is indeed a VRAD (very RAD). You can go from zero to information system in almost no time with almost no resources (the typical scenario of one developer mentioned previously). TH downside is that when you have this few people working on the system, it can be underdocumented. Which means that when your magical one-man development team jets, it's going to be easier to rewrite the application from scratch (and when that crisis comes, it's often rewritten in Access/VBA again, since a system is needed, FAST). Oh my aching bones...
3. Mentioned elsewhere, but these MS products are EOL'ed periodically. No support. No bug fixes. No security fixes. One often overlooked consequence of this is that MS drives the techie labor market towards its current offerings; what this means is that you are not going to expect a VB-based product to last, since a few years down the road the Microsoft marketing machine has changed the paradigm and driven developers towards other technologies, limiting the availability of engineers to feed your monster.
4. When you're developing a system for business usage, you're going to want to have several things which more proefessional toolchains make more readily expose; things which, more likely than not you can accomplish nominally in VB albeit with a lot of workaounds and in many cases not very reliably and sub-optimally. Audit trails, transaction atomicity, multi-user functionality, etc.
I'll post more if I canthink of them. Good to have a reference of VB drawbacks, especially since I see it so often.