Extracting a character - trivial.
Length of string - trivial.
I don't think it's quite as simple as you think. UTF-8 is a variable-length encoding, but UTF-32 is too when you consider grapheme clusters.
When you extract characters and and determine length, are you only talking about code points (not very useful) or are you taking into consideration combining characters to account for actual visible glyphs that most people would consider to be a character?
The overwhelming majority of apps are only doing trivial operations -- string concatenation and shuffling bits to some API to display text. For these apps, choice of encoding really does not matter. NetHack is very likely in this category.
Anything more and you'll have to deal with variable-length data for both UTF-8 and UTF-32. So it doesn't really matter. Choose whichever uses less storage space.
For which implimentation of UTF to use, I'd go with utf8 as it seems to have the widest adoption, or 32 because that will probably allow you the longest time before having to think about this again. I would avoid the middle ground.
UTF-8, while originally only defined to 31 bits and now defined to 21 bits, actually has room to trivially extend up to 43 bits. One could say it's more future-proof than UTF-32.
Not that it really matters -- we're only using 17 bits right now so I doubt we'll ever get past 21. Maybe when we encounter intelligent alien life.
No matter what your industry is, some PHB is going to get into a position where they feel out of control and unproductive if they can't get instant gratification popping in on their people to micro-manage them. In-person meetings are a must for these people.
You'll always have those insane people who think Vinyl has better quality than CDs or FLAC... but I imagine they are a pretty small group.
You've got people who're after the experience -- maybe a more personal feel to having a big physical system that needs more interaction. Again I imagine this is larger than the first group, but still relatively small.
And finally you've got hipsters, who'll do anything just because nobody else is doing it. Very suspicious that vinyl's popularity starts to grow with a strong correlation to this group's size.
So many people are panning this movie. Have you guys posting negative comments actually seen it, or are you just reacting to the press?
I mean, I get it -- there's bound to be some sort of automatic counter-culture response to defend against the massive amount of press talking about how controversial and important it is.
Yes, it's a little controversial to target an actual country and an actual leader so directly. But you know what, their message while embellished for comedic effect isn't really far off base. I think the world could use some more of this controversy, and there's nothing saying this type of thing needs to be in dry journalistic form.
As far as the movie itself goes --- it's a Seth Rogan bromance dick joke movie. It really doesn't bring anything new to the table. It's not his best movie, but it's by no means bad. It's fun and entertained me the whole way through.
They've already given word they intend to throw out comments that don't give an in-depth analysis... so the great majority of these comments that are just like "hey i use this stuff, please don't fuck with it" will just be ignored.
No. These are standard instructions that many apps require to function correctly when using multiple threads. Even if you aren't using them directly, at least some of the APIs you use most certainly are.
Makes you wonder what kind of good could have been done or how many lives could have been saved with that $70 million.
It's not like he's throwing bills into a fire. That money goes back into the economy which is good for everybody, and its recipients are still free to spend it on whatever good deeds they want.
I haven't seen any evidence that the mechanics of the attack itself is at all noteworthy, yet we keep hearing about how this attack was unstoppable, "nasty", etc. -- not just from Sony's PR guys, but from the FBI. As if it could have targeted literally any company and caused just as unmitigated damage.
To me, a "nasty" worm is Stuxnet: it spread in a very standard innocuous way and seemed like any other worm, but ended up being highly targeted.
This Sony hack just seems like your average trojan worm leaking an admin password back to someone. The only noteworthy part of this hack is that Sony had such horrifyingly moronic security practices that one attack was able to compromise such a large and varying corpus of valuable data.
Last flight I took out of LAX, they were randomly handing out "expedited security" slips to people. Keep your shoes on, laptops can stay in bags, no x-rays or pat-downs, etc. and I was through in about 30 seconds. I even found out after I went through the metal detector that I had left keys in my pocket and my belt on.
Basically, it was like security used to be, pre-9/11. It was marvelous.
Freenet had some issues. Most of them won't apply to BitTorrent's offering.
The main one is receiving content was dog slow compared to, say, Tor. This is simply an artifact of how it was routing connections and the distributed storage aspect.
Second, but still contributing to the poor experience is that the app itself had some architectural flaws that made it and your PC run dog slow -- the choice was either use hundreds of threads or let the operations stall.
The third, more of a security/philosophical flaw, is that the base protocol was not documented in any significant fashion. To review the protocol's security, you'd need to have an expert understanding of Java and a large part of the codebase. So it never really had many eyes on it looking for flaws.
I haven't used Freenet in around 5 years, so this may have improved. It was pretty clear why it never caught on at the time.
Merely needing to convert time zones is a trivial requirement. Work with them any other way and it's a nightmare. My first exposure to it was when implementing a crontab-like scheduling software, which on proper implementations has defined behavior to not fall on its face when daylight savings time wreaks havoc on the world. I couldn't find a way to do this reliably in.NET, but Noda made it possible.
Don't take my word on why Noda should be used though... read from it's blog for plenty of examples for why the seemingly great.NET DateTime can be a minefield in far more common situations than mine.
Why should I have to use a third party library to get decent date support?
I've questioned that myself while working in.NET. Ever needed to write time zone aware code?
Date libraries, as it turns out, are rather monstrously difficult to make. While.NET did a great job for the common stuff, uncommon things can be painful, error prone, or impossible.
The fullest solution I've found so far is Noda Time, which is actually based on the Joda-Time Java library. It feels out of place with a number of Javaisms still in it, but it provides a much richer functionality and better separation of concerns.
Recent video cards support encoding an H.264 stream directly from the screen without ever touching the CPU. If Steam isn't currently using this functionality, I'm sure it will soon.
The EU seems to have a chip on their shoulders about Google. I get it, they're huge and they need to be kept on a leash.
But when are we going to see them go after other huge companies abusing their market share? We have Amazon regularly putting full-page ads for their latest electronics right on their front page.
Hipster culture is like a passive-aggressive punk culture. Both have a distinctive styles of clothing, music, and a strong counter-culture attitude. The main differentiation is that hipsters are less raucous, less extreme.
The implication of this is that it's possible to clone a key based only on the signal it gives off. The implication of that is that they're sending out a static password.
Not only is it possible, but it's in common practice. Aftermarket remote starters need to clone your keys. You can get a remote starter for basically any car. It's not like you need a dealer for it either, because car electronics places that install these things will be the ones cloning the keys.
Some software projects like LAME, x264, and libav claim to skirt around patent issues by only distributing source code, not binaries. I've always wondered if this is a valid workaround, or just some clever devs getting their hopes up.
Is there a reason why it would be useful to make D3D 9 support more complete?
Games only started using D3D 10/11 *very* recently -- the back catalog this could enable is huge, and D3D 9 games are still coming out today. It'd say it's very important to support.
Slashdot Mirror
Extracting a character - trivial. Length of string - trivial.
I don't think it's quite as simple as you think. UTF-8 is a variable-length encoding, but UTF-32 is too when you consider grapheme clusters.
When you extract characters and and determine length, are you only talking about code points (not very useful) or are you taking into consideration combining characters to account for actual visible glyphs that most people would consider to be a character?
The overwhelming majority of apps are only doing trivial operations -- string concatenation and shuffling bits to some API to display text. For these apps, choice of encoding really does not matter. NetHack is very likely in this category.
Anything more and you'll have to deal with variable-length data for both UTF-8 and UTF-32. So it doesn't really matter. Choose whichever uses less storage space.
For which implimentation of UTF to use, I'd go with utf8 as it seems to have the widest adoption, or 32 because that will probably allow you the longest time before having to think about this again. I would avoid the middle ground.
UTF-8, while originally only defined to 31 bits and now defined to 21 bits, actually has room to trivially extend up to 43 bits. One could say it's more future-proof than UTF-32. Not that it really matters -- we're only using 17 bits right now so I doubt we'll ever get past 21. Maybe when we encounter intelligent alien life.
No matter what your industry is, some PHB is going to get into a position where they feel out of control and unproductive if they can't get instant gratification popping in on their people to micro-manage them. In-person meetings are a must for these people.
There are a few types I see doing this.
You'll always have those insane people who think Vinyl has better quality than CDs or FLAC... but I imagine they are a pretty small group.
You've got people who're after the experience -- maybe a more personal feel to having a big physical system that needs more interaction. Again I imagine this is larger than the first group, but still relatively small.
And finally you've got hipsters, who'll do anything just because nobody else is doing it. Very suspicious that vinyl's popularity starts to grow with a strong correlation to this group's size.
So many people are panning this movie. Have you guys posting negative comments actually seen it, or are you just reacting to the press?
I mean, I get it -- there's bound to be some sort of automatic counter-culture response to defend against the massive amount of press talking about how controversial and important it is.
Yes, it's a little controversial to target an actual country and an actual leader so directly. But you know what, their message while embellished for comedic effect isn't really far off base. I think the world could use some more of this controversy, and there's nothing saying this type of thing needs to be in dry journalistic form.
As far as the movie itself goes --- it's a Seth Rogan bromance dick joke movie. It really doesn't bring anything new to the table. It's not his best movie, but it's by no means bad. It's fun and entertained me the whole way through.
They've already given word they intend to throw out comments that don't give an in-depth analysis... so the great majority of these comments that are just like "hey i use this stuff, please don't fuck with it" will just be ignored.
No. These are standard instructions that many apps require to function correctly when using multiple threads. Even if you aren't using them directly, at least some of the APIs you use most certainly are.
Makes you wonder what kind of good could have been done or how many lives could have been saved with that $70 million.
It's not like he's throwing bills into a fire. That money goes back into the economy which is good for everybody, and its recipients are still free to spend it on whatever good deeds they want.
I haven't seen any evidence that the mechanics of the attack itself is at all noteworthy, yet we keep hearing about how this attack was unstoppable, "nasty", etc. -- not just from Sony's PR guys, but from the FBI. As if it could have targeted literally any company and caused just as unmitigated damage.
To me, a "nasty" worm is Stuxnet: it spread in a very standard innocuous way and seemed like any other worm, but ended up being highly targeted.
This Sony hack just seems like your average trojan worm leaking an admin password back to someone. The only noteworthy part of this hack is that Sony had such horrifyingly moronic security practices that one attack was able to compromise such a large and varying corpus of valuable data.
Funny, Microsoft has actually had a P2P DNS system for several years: PNRP.
Last flight I took out of LAX, they were randomly handing out "expedited security" slips to people. Keep your shoes on, laptops can stay in bags, no x-rays or pat-downs, etc. and I was through in about 30 seconds. I even found out after I went through the metal detector that I had left keys in my pocket and my belt on.
Basically, it was like security used to be, pre-9/11. It was marvelous.
Let us know which bank. I'm sure some of us would switch!
Freenet had some issues. Most of them won't apply to BitTorrent's offering.
The main one is receiving content was dog slow compared to, say, Tor. This is simply an artifact of how it was routing connections and the distributed storage aspect.
Second, but still contributing to the poor experience is that the app itself had some architectural flaws that made it and your PC run dog slow -- the choice was either use hundreds of threads or let the operations stall.
The third, more of a security/philosophical flaw, is that the base protocol was not documented in any significant fashion. To review the protocol's security, you'd need to have an expert understanding of Java and a large part of the codebase. So it never really had many eyes on it looking for flaws.
I haven't used Freenet in around 5 years, so this may have improved. It was pretty clear why it never caught on at the time.
Merely needing to convert time zones is a trivial requirement. Work with them any other way and it's a nightmare. My first exposure to it was when implementing a crontab-like scheduling software, which on proper implementations has defined behavior to not fall on its face when daylight savings time wreaks havoc on the world. I couldn't find a way to do this reliably in .NET, but Noda made it possible.
Don't take my word on why Noda should be used though... read from it's blog for plenty of examples for why the seemingly great .NET DateTime can be a minefield in far more common situations than mine.
Why should I have to use a third party library to get decent date support?
I've questioned that myself while working in .NET. Ever needed to write time zone aware code?
Date libraries, as it turns out, are rather monstrously difficult to make. While .NET did a great job for the common stuff, uncommon things can be painful, error prone, or impossible.
The fullest solution I've found so far is Noda Time, which is actually based on the Joda-Time Java library. It feels out of place with a number of Javaisms still in it, but it provides a much richer functionality and better separation of concerns.
.NET Core is the redesign.
.NET Framework (the full big monolithic install like we've got now) remains backwards-compatible and so 4.6 is appropriate.
Recent video cards support encoding an H.264 stream directly from the screen without ever touching the CPU. If Steam isn't currently using this functionality, I'm sure it will soon.
Why aren't companies paying more people to work on Open Source projects.
The EU seems to have a chip on their shoulders about Google. I get it, they're huge and they need to be kept on a leash. But when are we going to see them go after other huge companies abusing their market share? We have Amazon regularly putting full-page ads for their latest electronics right on their front page.
Multi-process is the major reason I use Chrome. One tab freezing up the entire app, or even just making other tabs slower, is unacceptable.
Then this hits general availability I'll definitely be re-evaluating Firefox.
Hipster culture is like a passive-aggressive punk culture. Both have a distinctive styles of clothing, music, and a strong counter-culture attitude. The main differentiation is that hipsters are less raucous, less extreme.
I have the issue, and no other media player does this. Either everyone is working around it and being silent about how, or this is a Chrome bug.
The implication of this is that it's possible to clone a key based only on the signal it gives off. The implication of that is that they're sending out a static password.
Not only is it possible, but it's in common practice. Aftermarket remote starters need to clone your keys. You can get a remote starter for basically any car. It's not like you need a dealer for it either, because car electronics places that install these things will be the ones cloning the keys.
Some software projects like LAME, x264, and libav claim to skirt around patent issues by only distributing source code, not binaries. I've always wondered if this is a valid workaround, or just some clever devs getting their hopes up.
Is there a reason why it would be useful to make D3D 9 support more complete?
Games only started using D3D 10/11 *very* recently -- the back catalog this could enable is huge, and D3D 9 games are still coming out today. It'd say it's very important to support.