I turn on extensions and set my default view to Details sorted by extension.
Also, ban spaces in directory and file names (as well as dots so the Anna.gif.exe is invalid). Spaces in names is a pain when you're typing at the command line......who wants to have to type quotes around their file names?
When I was learning recursion (eons ago, it seems), I was informed that both head and tail recursion could be "unrolled" to a loop of some sort (for, while, do....while, do...until, etc.) And recursion imparts a lot of overhead (push to stack, context switch, process, pop from stack), so you should unroll recursive functions as often as possible.
So, in this example, I don't think most people would think to use recursion at all --- head, tail, or mid recursion.
It's less of an issue of recreating all of the "basic" controls and more a factor of every single designer wants to style buttons differently. You either buy into the native aesthetics or you don't complain when you don't have a native experience.
It may be the second or third most spoken IRL, but in terms of off-shoring, most of the jobs go to places that speak English (India), Chinese (China), Russian (Russia), and Portuguese (Brazil). So, knowing Spanish or French isn't as useful *in his profession*.
PII should be classified based on sensitivity. At a certain level, that PII must be encrypted during transit. At the highest level, it must be encrypted during transit and at rest. SSN falls in the highest sensitivity level. SOP for years. This doesn't guarantee you won't get hacked, but it reduces / minimizes the impact if you are hacked.
PII - Personally Identifiable Information SSN - Social Security Number SOP - Standard Operating Procedure
(per the video description) From Los Angeles, you'd next see it in 2023. Which to me means that it isn't as rare as implied (unless it's like primes where there are some close ones and some far ones and the next next one would be hundreds of years later).
I did.....mostly because I probably won't watch it live. While neat from a rarity stance, it doesn't have much scientific relevance that I can think of. Cool, but the video is good enough for me.
I'd argue C# and then Java because the non-programming pieces are "pointy-clicky, draggy-droppy". Running your web based code in IIS doesn't take a lot of knowledge about how to get IIS up and running --- whereas trying to do the same with something like tomcat is a pain for someone who is already struggling to learn programming. [Plus, Visual Studio is a very developer-friendly IDE.]
Basically, remove all of the pain points so that they can focus on learning to code....... (for those of you who argue the using Microsoft products is enough of a pain point, it's easier for a noob than learning Linux because of the aforementioned pointy-clicky, draggy-droppy approach.....)
I think Javascript is a good choice in terms of barrier to entry and examples available online. The only thing I dislike is that it is a dynamic language -- and I think that people learning to program need a very structured language as they are learning (protect them from their ignorance).
I disagree with your coder lock-in statement. But I agree with your "throw a dart" metaphor.
Just because you CAN code an algorithm in a language doesn't mean it's the best option. Just because I can drive a screw into a 2x4 with the heel of my shoe doesn't mean I should.
Languages are developed to make certain problem domains easier. If they are flexible enough, people will adopt them for other problem domains as well. If they aren't flexible enough, they might stick around in their problem domain, but they'll stay on the outskirts. That's it.
Very true. For "the common man" to know what direction to take, too many choices can be bad......especially when there is more similarity than differences and not enough experience to know which differences will be important to them in the future.
But you should be able to cache the unchanging portions (the template as it were) and not cache the data leading to BETTER caching. If I'm using some sort of data-binding and AJAX, my HTML template page and the Javascript logic can both be cached. Then, my page can be dynamically (and constantly) updated with AJAX data. As the data changes, I don't have to keep sending an entirely new HTML page that only differs by some portion of the content.
All of the reasons that you like Java are the very same reasons that I opt to feed my family coding in the various.Net technologies (ASP.NET, C#, Javascript, HTML, etc.). Microsoft is very developer friendly (just as Balmer).....but seriously, Visual Studio is a great IDE.
But I firmly agree with the aspect of taking less money to do what you love; that's far more important than money. My worst day doing my current job is better than the best day at my previous job.
For those people, the experience on lower-end Windows Phone devices is usually better than the experience on lower-end Android devices......I suspect that's where MS will garner their greatest bump in marketshare.
An unlocked Lumia device for under $100 US ---- unsubsidized!!! And it's actually a decent phone for the money and doesn't suffer as much UI stutter as a knock-off Android device.
I still have my copy as well, but I haven't fired it up in a while (emulators!).
But those Atari 2600 carts were pretty robust.....just ask any of the ones that were flung across my room. I would bet that a cart wrapped in cardboard survived rather well.
This. Languages that enforce their rules at compile time vs run time should inherently lead to higher quality code just by "accident". You can still write bad (or good) code in any language, but a language that lets you do whatever you want requires you to be much more rigorous in your testing strategy to ensure higher quality......and we all know how much developers love to test (and to document).
Can't we sick Greenpeace on PETA -- get two of most polarizing groups fighting each other? The camel wasn't injured (was probably well taken care of) and was more environmentally friendly than a Jeep.
Most of the solutions for harnessing wave power that I've seen rely on something staying moored in the same place and letting the waves go back and forth over the device. So, a boat anchored for a time could use a similar device (probably combined with something to harness the sun and winds, too -- power needs probably exceed the generation capabilities of each of them individually). While the boat is moving, you have an engine which can generate power as well as locomotion. So, I don't really see the problem with it.
Slashdot Mirror
I turn on extensions and set my default view to Details sorted by extension.
Also, ban spaces in directory and file names (as well as dots so the Anna.gif.exe is invalid). Spaces in names is a pain when you're typing at the command line......who wants to have to type quotes around their file names?
When I was learning recursion (eons ago, it seems), I was informed that both head and tail recursion could be "unrolled" to a loop of some sort (for, while, do....while, do...until, etc.) And recursion imparts a lot of overhead (push to stack, context switch, process, pop from stack), so you should unroll recursive functions as often as possible.
So, in this example, I don't think most people would think to use recursion at all --- head, tail, or mid recursion.
It's less of an issue of recreating all of the "basic" controls and more a factor of every single designer wants to style buttons differently. You either buy into the native aesthetics or you don't complain when you don't have a native experience.
It may be the second or third most spoken IRL, but in terms of off-shoring, most of the jobs go to places that speak English (India), Chinese (China), Russian (Russia), and Portuguese (Brazil). So, knowing Spanish or French isn't as useful *in his profession*.
PII should be classified based on sensitivity. At a certain level, that PII must be encrypted during transit. At the highest level, it must be encrypted during transit and at rest. SSN falls in the highest sensitivity level. SOP for years. This doesn't guarantee you won't get hacked, but it reduces / minimizes the impact if you are hacked.
PII - Personally Identifiable Information
SSN - Social Security Number
SOP - Standard Operating Procedure
(per the video description) From Los Angeles, you'd next see it in 2023. Which to me means that it isn't as rare as implied (unless it's like primes where there are some close ones and some far ones and the next next one would be hundreds of years later).
I did.....mostly because I probably won't watch it live. While neat from a rarity stance, it doesn't have much scientific relevance that I can think of. Cool, but the video is good enough for me.
I'd argue C# and then Java because the non-programming pieces are "pointy-clicky, draggy-droppy". Running your web based code in IIS doesn't take a lot of knowledge about how to get IIS up and running --- whereas trying to do the same with something like tomcat is a pain for someone who is already struggling to learn programming. [Plus, Visual Studio is a very developer-friendly IDE.]
Basically, remove all of the pain points so that they can focus on learning to code....... (for those of you who argue the using Microsoft products is enough of a pain point, it's easier for a noob than learning Linux because of the aforementioned pointy-clicky, draggy-droppy approach.....)
I think Javascript is a good choice in terms of barrier to entry and examples available online. The only thing I dislike is that it is a dynamic language -- and I think that people learning to program need a very structured language as they are learning (protect them from their ignorance).
I was the kid that would do extraneous proofs in Geometry just so I could use those theorems later on in the test.
My (limited understanding) is no.....but fewer of them "clog the pipe" and make it to the other end (lower resistance values).
I disagree with your coder lock-in statement. But I agree with your "throw a dart" metaphor.
Just because you CAN code an algorithm in a language doesn't mean it's the best option. Just because I can drive a screw into a 2x4 with the heel of my shoe doesn't mean I should.
Languages are developed to make certain problem domains easier. If they are flexible enough, people will adopt them for other problem domains as well. If they aren't flexible enough, they might stick around in their problem domain, but they'll stay on the outskirts. That's it.
Very true. For "the common man" to know what direction to take, too many choices can be bad......especially when there is more similarity than differences and not enough experience to know which differences will be important to them in the future.
But you should be able to cache the unchanging portions (the template as it were) and not cache the data leading to BETTER caching. If I'm using some sort of data-binding and AJAX, my HTML template page and the Javascript logic can both be cached. Then, my page can be dynamically (and constantly) updated with AJAX data. As the data changes, I don't have to keep sending an entirely new HTML page that only differs by some portion of the content.
All of the reasons that you like Java are the very same reasons that I opt to feed my family coding in the various .Net technologies (ASP.NET, C#, Javascript, HTML, etc.). Microsoft is very developer friendly (just as Balmer).....but seriously, Visual Studio is a great IDE.
But I firmly agree with the aspect of taking less money to do what you love; that's far more important than money. My worst day doing my current job is better than the best day at my previous job.
After Egypt might be a fun game.......sort of an RPG that reminds me of Wasteland......
This is one of the reasons that I kill the Chrome task if I get anything even remotely fishy (phishy) looking popping up.
Turn around.....the congregation is over there. This is the choir. But preach on.
For those people, the experience on lower-end Windows Phone devices is usually better than the experience on lower-end Android devices......I suspect that's where MS will garner their greatest bump in marketshare.
An unlocked Lumia device for under $100 US ---- unsubsidized!!! And it's actually a decent phone for the money and doesn't suffer as much UI stutter as a knock-off Android device.
Does it ensure that your Stripper name is protected akin to a business license? That would be a useful benefit of registering.
I still have my copy as well, but I haven't fired it up in a while (emulators!).
But those Atari 2600 carts were pretty robust.....just ask any of the ones that were flung across my room. I would bet that a cart wrapped in cardboard survived rather well.
This. Languages that enforce their rules at compile time vs run time should inherently lead to higher quality code just by "accident". You can still write bad (or good) code in any language, but a language that lets you do whatever you want requires you to be much more rigorous in your testing strategy to ensure higher quality......and we all know how much developers love to test (and to document).
Can't we sick Greenpeace on PETA -- get two of most polarizing groups fighting each other? The camel wasn't injured (was probably well taken care of) and was more environmentally friendly than a Jeep.
Another feature that I would love to see in CSS is "relative to another element" via a selector.
Some Content
That is multiple lines tall
More Content
height: ||.SomeContainer||.height
}
That should make layout simpler.
Most of the solutions for harnessing wave power that I've seen rely on something staying moored in the same place and letting the waves go back and forth over the device. So, a boat anchored for a time could use a similar device (probably combined with something to harness the sun and winds, too -- power needs probably exceed the generation capabilities of each of them individually). While the boat is moving, you have an engine which can generate power as well as locomotion. So, I don't really see the problem with it.