Hello? Most of you missed to real point: all those languages and frameworks are huge and most of the time insanely complex pieces of software. And that's really bad (just have a look at perl code, openjdk code or mono code). We are talking about millions of complex line of code, most of the time requiring the complexity of an optimizing C++ compiler... that's sick... The most reasonable option is to take into account the whole software stack and reduce to the maximum its size and complexity.
Then I stick to C and only C and keep in mind all the time maintainability. As far as I'm concern the upper threshold of complexity and size is (linux+optimizing C toolchain). Then I build everything on top of this software stack and no more.
Indeed its code is such a macro hell, and so complex and so huge that "almost" nobody dares to clean its code base. But if there is a bug, BOOM! C and only C for GNU/Linux or die
If you look at the open source drivers for GPUs, those are full of bugs, that means that this chip will have to deal with the bugs of ALL GPUs... Bare non-sense.
The USA have a bigger problem to attend: most of the country was shaped on "oil high availability". The increase of the ratio (oil cost)/(household buying power) will have dramatic effects since the dependency is quite high.
Basically, the USA do not have to waist their time on ADSL or such. If they have to spend "energy" that would be for the final IPv6/FTTH/mobile internet. Let Japan(asia?) and Europe fine tune this internet, then use the matured technology.
If anybody improves, corrects any bugs that would run in Linux, the GNU GPL prevails: those improvements and correction has to go public.
God I love that license!
Really tiring... really...
Still C++... should require C compiler complexity only
Bazare is... well, should go for GIT instead.
And GPL for what, since we have to surrender our GPL rights to a for-profit organisation(Sun upper management and board) and in no case I would like to have my code in their closed proprietary forks... We need a Linux-spirit-like SQL DB engine for God Sake!
When the media player DOM and the will be in most browsers and once main video web sites support all that media boiler plate, people may think its a good incentive to upgrade.
Of course, tamarin (the adobe mozilla pet project that will be used to take over mozilla and screw the web) is written using C, isn't it?
Or, is this a C++ bloat doomed to trash mozilla spidermonkey, the C coded webscript interpreter?
Really I wonder, really...
Hope that in this alpha release we will have the element with the DOM minimal media player!
Because, the main video sites will have to provide beta testing quickly for that player: finally the video for the web!
The serious answer to this issue is IPv6 with traffic classes *and* support from IAPs. Of course "standardized" traffic classes will have to cross IAPs boundaries (That would be enforced by a government regulation authority).
In the IPv6 header you have a traffic class field and a flow id. Network equipement could do traffic shaping at a very low level of channels/flows thanks to those and the other header fields. But carefull, where shaping happens, unfairness between users can happen, so fairness of bandwidth in each traffic class between users must be enforced: net neutrality.
The thing which seems to be missing: how your soft phone will discover the traffic classes, numbers of flows per traffic class and the bandwidth limitation of the each flow, all that per internet access point of your IAP?
If it's not under the GPL license, it will end like MacOS and BSD: the open source version will be crippled and hardly usable/installable on terminal hardware...
If the XBOX is a money sink, The Great Evil would not be allowed to sell it.
Indeed, most of the laws in main XBOX client countries forbids the practice of product dumping (or in only very specific cases). So the XBOX would be sold at its manufacturing cost price without margin.
But since we are in the middle of globalization and there are many financial trickeries now possible... I would not bet on a fair respect of the laws. International finance gives international corporations the tools required to quite easily work around many finance regulation laws (... and to boost corruption).
And you missed something: if those companies have a trick to make people spend more money on their hardware, then they will use it. They are not angels. If they make a loss on raw XBOX sales, the margin of mod chips, if from them, will reduce that loss. So making mod chips part of their business model is consistent in both cases.
It's overboard to dissalow GNU/Linux to fully use the hardware you bought by default.
Mod chips are here to insure proper balance.
Actually, I think explicit locking of hardware with an OS is illegal in many countries.
Maybe mod chips are part of their business model: they say mod chips are bad, but behind the scene if you look carefully, they actually sell them!
Because at the end, that makes people spending more money on their hardware...
Open standards are not sufficient enought. You can slip to a monopoly with an open standard which is so complex that only one piece of software can deal with it properly (cf. OOXML).
The idea would be that the IAPs should split their bandwidth fairly among all their users. In its bandwidth share, the user should prioritize its outgoing traffic. The IAP should shape the incomming traffic fairly between each of its user.
In this scenario, low latency network applications are dead (video conferencing/telephony/video games...): in an home network lan, the momy is watching a HD internet TV channel, the boy can forget playing online its favorite FPS and the girl cannot have a decent IP phone line call. That's why there is a exception to let the IAP to shape further specifically on low lantency protocols... but they will never be able to embrace all past-present-futur low latency protocols on the net. Of course they could favor only the protocols of big bucks corporations. So you could trash any open low latency protocols...
But there is a another way: IPv6. Indeed the protocol does have labels that let you tag traffic. Its means the user network apps can tell the IAP equipement what type of traffic they send. So the IAPs can apply shaping rules based on that type of traffic on cross-user boundaries. Nethertheless in a traffic priority class, the IAP still has to provide fairness among users.
Basically, fairness among user is not applied on traffic as a whole but on a per traffic class basis.
Of course in the real world, low latency traffic will have to be shaped to very small bandwidth... smart users would push their P2P traffic on high priority. The idea on high priority traffic classes is to have just enough bandwidth to let signaling, highly compressed voice, intense action FPS game data. Of course, you can have several high priority classes. BUT there is a BIG exception to all of this, emergency services: for instance you want to call from the net the "internet US 911". In this case the IAP equipement will have to know without IPv6 label that you are calling an emergency service (IP based shaping, but amount of IPs must be minimal to avoid overloaded routing tables and increased latency that will degrade internet quality significantly).
I let you imagine what it will be when users will have Fiber To The Home with upload bandwidth on a 100's of Mb scale!
This does mean, rewritting many network applications. Deep IAP topology reconfiguration. More expensive IAP equipements: must be able to perform shaping extremely quickly in order to minimize the latency cost(=forget high level protocol shaping or shaping based on too much data(IPs)).
Indeed, I do not count the proprietary forks of pieces of open source software released on a not protective enough licence with "added closed and proprietary value" in them. The risk is to make the open source version crippled for proper use on purpose compared to proprietary forks.
The companies or people using such naughty tricks are not a issue with the enforcement of fairness through the GPL licence: if you use a GPL piece of software, the GPL guaranties that any modifications, if distributed, remains under the GPL and must be published.
... your viruses and pieces of spyware!
SP3 broke them! Well, wait for the next auto update of your prefered virus and spyware (without your consent of course!), it will fixe everything and your computer will be a nice zombie again.
Who is he? What's his name, can we have a picture of him? I know that people can change but shall we add him to the community databases of guys to watch?
It's like cards in a pokemon games... instead of monsters we have those guys... quite related, aren't they? And we exchange the cards, talk about those monsters...
As a security and privacy feature, people shall now start to deploy full encrypted trackers on which only people they know can connect to (password or PSK). And that additionally to "public" trackers.
Another thing, some transports should be able to hide randomly torrent traffic in well known protocols in order to avoid CPU efficient detection. Torrent traffic means data and control stuff from the tracker and other peers. The idea is to make tracking torrent users unreasonable and inefficient regarding net performance. Namely, torrent user tracking will cost a lot and would kill net efficiency.
Slashdot Mirror
Conclusion: you keep your entire software stack minimal and try hard to avoid the quick and dirty hack = maximal control
:)
Hello?
Most of you missed to real point: all those languages and frameworks are huge and most of the time insanely complex pieces of software. And that's really bad (just have a look at perl code, openjdk code or mono code). We are talking about millions of complex line of code, most of the time requiring the complexity of an optimizing C++ compiler... that's sick...
The most reasonable option is to take into account the whole software stack and reduce to the maximum its size and complexity. Then I stick to C and only C and keep in mind all the time maintainability. As far as I'm concern the upper threshold of complexity and size is (linux+optimizing C toolchain). Then I build everything on top of this software stack and no more.
Yes! http://www.suckless.org/common/index.html
Well, it's notorious. It's like Novell is the open source company of MS.
Indeed its code is such a macro hell, and so complex and so huge that "almost" nobody dares to clean its code base. But if there is a bug, BOOM!
C and only C for GNU/Linux or die
Buy the Freerunner... do not bother with phones which are not even open source now.
If you look at the open source drivers for GPUs, those are full of bugs, that means that this chip will have to deal with the bugs of ALL GPUs... Bare non-sense.
The USA have a bigger problem to attend: most of the country was shaped on "oil high availability". The increase of the ratio (oil cost)/(household buying power) will have dramatic effects since the dependency is quite high. Basically, the USA do not have to waist their time on ADSL or such. If they have to spend "energy" that would be for the final IPv6/FTTH/mobile internet. Let Japan(asia?) and Europe fine tune this internet, then use the matured technology.
HuHo! Flash is outside the open source stack... That will allow us to get rid of this proprietary plugin for good.
If anybody improves, corrects any bugs that would run in Linux, the GNU GPL prevails: those improvements and correction has to go public. God I love that license!
Really tiring... really... Still C++... should require C compiler complexity only ... well, should go for GIT instead.
Bazare is
And GPL for what, since we have to surrender our GPL rights to a for-profit organisation(Sun upper management and board) and in no case I would like to have my code in their closed proprietary forks...
We need a Linux-spirit-like SQL DB engine for God Sake!
When the media player DOM and the will be in most browsers and once main video web sites support all that media boiler plate, people may think its a good incentive to upgrade.
Of course, tamarin (the adobe mozilla pet project that will be used to take over mozilla and screw the web) is written using C, isn't it? Or, is this a C++ bloat doomed to trash mozilla spidermonkey, the C coded webscript interpreter? Really I wonder, really...
Hope that in this alpha release we will have the element with the DOM minimal media player! Because, the main video sites will have to provide beta testing quickly for that player: finally the video for the web!
The serious answer to this issue is IPv6 with traffic classes *and* support from IAPs. Of course "standardized" traffic classes will have to cross IAPs boundaries (That would be enforced by a government regulation authority). In the IPv6 header you have a traffic class field and a flow id. Network equipement could do traffic shaping at a very low level of channels/flows thanks to those and the other header fields. But carefull, where shaping happens, unfairness between users can happen, so fairness of bandwidth in each traffic class between users must be enforced: net neutrality. The thing which seems to be missing: how your soft phone will discover the traffic classes, numbers of flows per traffic class and the bandwidth limitation of the each flow, all that per internet access point of your IAP?
If it's not under the GPL license, it will end like MacOS and BSD: the open source version will be crippled and hardly usable/installable on terminal hardware...
If the XBOX is a money sink, The Great Evil would not be allowed to sell it. Indeed, most of the laws in main XBOX client countries forbids the practice of product dumping (or in only very specific cases). So the XBOX would be sold at its manufacturing cost price without margin. But since we are in the middle of globalization and there are many financial trickeries now possible... I would not bet on a fair respect of the laws. International finance gives international corporations the tools required to quite easily work around many finance regulation laws (... and to boost corruption). And you missed something: if those companies have a trick to make people spend more money on their hardware, then they will use it. They are not angels. If they make a loss on raw XBOX sales, the margin of mod chips, if from them, will reduce that loss. So making mod chips part of their business model is consistent in both cases.
It's overboard to dissalow GNU/Linux to fully use the hardware you bought by default. Mod chips are here to insure proper balance. Actually, I think explicit locking of hardware with an OS is illegal in many countries. Maybe mod chips are part of their business model: they say mod chips are bad, but behind the scene if you look carefully, they actually sell them! Because at the end, that makes people spending more money on their hardware...
Open standards are not sufficient enought. You can slip to a monopoly with an open standard which is so complex that only one piece of software can deal with it properly (cf. OOXML).
The idea would be that the IAPs should split their bandwidth fairly among all their users. In its bandwidth share, the user should prioritize its outgoing traffic. The IAP should shape the incomming traffic fairly between each of its user. In this scenario, low latency network applications are dead (video conferencing/telephony/video games...): in an home network lan, the momy is watching a HD internet TV channel, the boy can forget playing online its favorite FPS and the girl cannot have a decent IP phone line call. That's why there is a exception to let the IAP to shape further specifically on low lantency protocols... but they will never be able to embrace all past-present-futur low latency protocols on the net. Of course they could favor only the protocols of big bucks corporations. So you could trash any open low latency protocols...
But there is a another way: IPv6. Indeed the protocol does have labels that let you tag traffic. Its means the user network apps can tell the IAP equipement what type of traffic they send. So the IAPs can apply shaping rules based on that type of traffic on cross-user boundaries. Nethertheless in a traffic priority class, the IAP still has to provide fairness among users. Basically, fairness among user is not applied on traffic as a whole but on a per traffic class basis.
Of course in the real world, low latency traffic will have to be shaped to very small bandwidth... smart users would push their P2P traffic on high priority. The idea on high priority traffic classes is to have just enough bandwidth to let signaling, highly compressed voice, intense action FPS game data. Of course, you can have several high priority classes. BUT there is a BIG exception to all of this, emergency services: for instance you want to call from the net the "internet US 911". In this case the IAP equipement will have to know without IPv6 label that you are calling an emergency service (IP based shaping, but amount of IPs must be minimal to avoid overloaded routing tables and increased latency that will degrade internet quality significantly).
I let you imagine what it will be when users will have Fiber To The Home with upload bandwidth on a 100's of Mb scale!
This does mean, rewritting many network applications. Deep IAP topology reconfiguration. More expensive IAP equipements: must be able to perform shaping extremely quickly in order to minimize the latency cost(=forget high level protocol shaping or shaping based on too much data(IPs)).
And the last but not the least... IPv6!
Indeed, I do not count the proprietary forks of pieces of open source software released on a not protective enough licence with "added closed and proprietary value" in them. The risk is to make the open source version crippled for proper use on purpose compared to proprietary forks. The companies or people using such naughty tricks are not a issue with the enforcement of fairness through the GPL licence: if you use a GPL piece of software, the GPL guaranties that any modifications, if distributed, remains under the GPL and must be published.
... your viruses and pieces of spyware! SP3 broke them! Well, wait for the next auto update of your prefered virus and spyware (without your consent of course!), it will fixe everything and your computer will be a nice zombie again.
Who is he? What's his name, can we have a picture of him? I know that people can change but shall we add him to the community databases of guys to watch? It's like cards in a pokemon games... instead of monsters we have those guys... quite related, aren't they? And we exchange the cards, talk about those monsters...
As a security and privacy feature, people shall now start to deploy full encrypted trackers on which only people they know can connect to (password or PSK). And that additionally to "public" trackers. Another thing, some transports should be able to hide randomly torrent traffic in well known protocols in order to avoid CPU efficient detection. Torrent traffic means data and control stuff from the tracker and other peers. The idea is to make tracking torrent users unreasonable and inefficient regarding net performance. Namely, torrent user tracking will cost a lot and would kill net efficiency.
DAMN IT! We want opened drivers!