I have the iPhone X, and I stopped using the Ookla app months ago after I discovered that it was giving me incorrectly slow results. When I use the dslreports speed test, I consistently get the speeds I expect to see on any given wifi network; however, the Ookla app shows a much slower speed (consistently) on those same networks. When running these speed tests over cellular, I observe the same issue. This observation led me to conclude that the software was no longer useful, and possibly had gone unmaintained.
However, if theyâ(TM)re advertising this data as factual, it leads me to believe they may be doing this as an anti Apple campaign. This makes me wonder if Samsung (or another company) has paid them under the table to do this.
Seriously, we should all start boycotting companies which do this. There are enough of us now to make an impact. If we can convince our friends and families to boycott, too, it will make it more expensive to hire H1Bs than it is to hire Americans. We need to stop idly watching from the sidelines and do something about this. If we don't, they're free to use, abuse, and discard us with impunity.
I was 7 when I learned to program. I was taught how to draw graphics in BASIC on an Apple ][. Not having to draw every point manually was a great motivation to learn loops. The rest is history.
Kids love graphics and quick results. These days, I would teach a kid programming in Swift, if you have a Mac, because the instantaneous results in the other pane and the graphics and animation capabilities will make it fun. If it, I'd use Python, because I've been calling it the new Basic for years. All the beginner programmers immediately get defensive when I say that, while the more experienced ones chuckle. Proof enough that it's the new Basic?
Remember, it doesn't need to be writing a game to make it fun. That's a little too tough at age 7; not because the programming for a simple game is tough, but because kids that age usually can't yet wrap their heads around what makes games fun. Because of this, they have a really hard time coming up with something fun, and they can end up disillusioned from the experience of doing a lot of hard work just to make something boring. Also, remember that what makes programming fun is the reward from figuring out how to make something work, so at this age, resist teaching data structures and algorithms. Instead, just give some trivial examples and let them play.
If you really want to tinker with that old technology, why don't you start out right by making it useful? Install Linux on it. It's too slow for Android, but you could try Firefox OS on it. Then you wouldn't be wasting your time learning an api for a dead OS.
It sounds like you're using the GPU as a DSP. Why not just get an embedded processor with a built in DSP? An example of an older generation one is the Atmel at9g45m. This is an older ARM core processor which has more power than you would expect. You can probably get away with using a fanless ARM system for your application. You may even find one that has enough processing power which doesn't even need a heatsink.
What can you do in Slackware that is impossible in Ubuntu?
In Slackware, you learn how to do things on any Linux distro. In Ubuntu, you only learn how to do things in Ubuntu, Debian, and Debian derivatives. I owe to Slackware the fact that I can sit down and work with any Linux distro out there. It doesn't include its own special tools for anything, so you are forced to do everything the "standard Linux way," which is the way that works on every distro (with some special exceptions, like DSL).
I would teach them basic bash scripting, and about/proc and/sys. Then I would have them write scripts to automate extracting information from/proc and/sys in bash using grep, sed and maybe awk. Teaching them how to work with Linux from the shell and how to pull information out of the kernel like this should give them some good insights into the operating system and its tools.
Additionally, I would teach them how to write init scripts and how to do "fun" things to get them excited about Linux.
I had the same dilemma, except I also knew I would eventually add 3D graphics as well. I wanted it to be portable to anything, and I needed it to render accurately and with proper anti-aliasing (anti-aliased while drawing, not via a filter after the fact). After mulling over all the options, I came to a difficult conclusion: write it myself. This is more work than I'd like, but it allows me to ensure it will run on anything, anywhere. If something new comes out that I want it to run on, I just port to it; I don't have to beg a vendor for it to be ported for me. Performance isn't paramount to my application, so I can put enough abstraction layers in to make the porting process relatively easy. All frameworks seem to put performance as the highest priority, which gets rid of the ease of portability. If your application will render graphics that sit still most of the time, this may be your best option (assuming you know linear algebra if you want vector graphics, and know graphics programming regardless).
You'll find getting back into the field, to program in high level languages with all of your previous experience outdated, to be very difficult. Companies will not want to pay you the salary your years of experience would warrant, and it would be like starting over.
Instead, the method back in that I've found for those of us who started in the "old days" is to go for embedded systems development. The embedded world uses 10+ year old technologies, so your experience with assembly language programming and writing software for systems with limited amounts of RAM and storage space is a big plus for embedded systems development. There are plenty of companies still creating software for processors that run at between 4 and 20 MHz with anywhere from 256 bytes of RAM on up to a handful of kilobytes of RAM. I've found this sort of development work is much more interesting, anyway, and people with old school knowledge are considered more valuable, rather than a dinosaur, for such work.
For such an expensive rocket launch, you'd think they'd at least have a professional photographer with professional lenses. Those pictures are terrible. Look at the flames; there's no detail. They obviously used cheap lenses. I'm an amateur photographer, but I have professional equipment because I'm too picky to have my pictures look as bad as their launch pictures do. I'm glad the launch succeeded, but you'd think they'd want better pictures for examining the launch and for PR.
He apparently wants us to take a step backwards to the days when crashes were frequent, such as with Windows 98. Software quality has a long way to go already. Does he not realize that making programmers deal with such an issue would bring software quality back into the Dark Ages?
As it is, programmers aren't given enough time to write software that works bug-free. Schedules are always rushed. This would dramatically increase: the burden on developers, the quantity of bugs, the number of developers being fired because they didn't get a project accomplished nearly as quickly as someone who pulled off a similar project 5 years earlier, the frustration of the users and developers (and transitively, the number of heart attacks around the world due to elevated blood pressure), the number of security vulnerabilities in software, and the migration rate to processor vendors who didn't make this mistake.
1. Make sure you have an Enterprise licensed AV installed. The per-client cost is low, and the updates will be centrally managed by the server. If your network is too small for this to be cost effective, then just have Norton AV (or your favorite respected AV) on every machine in the network.
2. Don't give your employees local admin privs. This one change has, in my experience, made all the difference in the world for many small businesses.
This is much cheaper than paying the labor for having an IT person come in and clean up all the messes.
I don't know about you, but I don't want to be anywhere a nuclear reactor that Bill Gates had any part in designing. It's bad enough that computers running software he had a hand in creating have orders of magnitude more problems than software from any other source. Put Bill Gates into the nuclear reactor business, and... well, I shudder to think of the sheer magnitude of the potential for disaster there.
I go with ext3 for this personally. NTFS doesn't store *nix style filesystem permissions, and causes various other issues with you Linux systems. With ext3, you can store all your files with all of your permissions intact, the filesystem is mature and trustworthy, and you can still access all of the files from any operating system by simply connecting the drives to a dedicated fileserver machine (an older computer or small device works perfectly for this). Simply share your files via NFS, Samba and ftp (if you need ftp access for something like xmbc). Having a dedicated machine for this means you can also script your replication to the secondary drive, so that you only have to attach the drive for the mirroring process to take place.
This is the solution I've been using for about four years now, and it works great for me.
That's easy! Switch them to Linux, where the devs weren't too shortsighted to realize that it would be a good idea to make everything on the desktop scalable. I run at my native resolution, which would make things a bit small for me, but all I have to do is set the monitor DPI to a higher value than actual, and everything appears at a nice, easily readable size.
How about a Mac Mini with a remote control? They have good audio hardware, you can connect it to your network wirelessly, and you can use Mac OS X, Linux or Windows on it for playing audio. They're also small, nearly silent, and women think they're cute.
No pictures? How can they not show us any pictures of this? And why a joystick? Why not something more like a brainwave scanner? That way, when you're talking on the cellphone, and you get distracted by picturing what the person on the other end is saying, you crash into a wall! That would be so cool!
This is why I only ask musicians who are good at what they do for advice on audio equipment. If you want to know what's good, you have to ask a musician who's passionate about music. Musicians know what the music is supposed to sound like because they've spent countless hours learning songs and practicing their craft. By listening to them, I have a setup that's so good it's made me turn and look behind me more than a few times because I swore the noise was made by something in the room.
KRK Rokit Studio monitors with a BBE Sonic Maximizer, in case you're wondering.
Slashdot Mirror
I have the iPhone X, and I stopped using the Ookla app months ago after I discovered that it was giving me incorrectly slow results. When I use the dslreports speed test, I consistently get the speeds I expect to see on any given wifi network; however, the Ookla app shows a much slower speed (consistently) on those same networks. When running these speed tests over cellular, I observe the same issue. This observation led me to conclude that the software was no longer useful, and possibly had gone unmaintained. However, if theyâ(TM)re advertising this data as factual, it leads me to believe they may be doing this as an anti Apple campaign. This makes me wonder if Samsung (or another company) has paid them under the table to do this.
Seriously, we should all start boycotting companies which do this. There are enough of us now to make an impact. If we can convince our friends and families to boycott, too, it will make it more expensive to hire H1Bs than it is to hire Americans. We need to stop idly watching from the sidelines and do something about this. If we don't, they're free to use, abuse, and discard us with impunity.
I was 7 when I learned to program. I was taught how to draw graphics in BASIC on an Apple ][. Not having to draw every point manually was a great motivation to learn loops. The rest is history. Kids love graphics and quick results. These days, I would teach a kid programming in Swift, if you have a Mac, because the instantaneous results in the other pane and the graphics and animation capabilities will make it fun. If it, I'd use Python, because I've been calling it the new Basic for years. All the beginner programmers immediately get defensive when I say that, while the more experienced ones chuckle. Proof enough that it's the new Basic? Remember, it doesn't need to be writing a game to make it fun. That's a little too tough at age 7; not because the programming for a simple game is tough, but because kids that age usually can't yet wrap their heads around what makes games fun. Because of this, they have a really hard time coming up with something fun, and they can end up disillusioned from the experience of doing a lot of hard work just to make something boring. Also, remember that what makes programming fun is the reward from figuring out how to make something work, so at this age, resist teaching data structures and algorithms. Instead, just give some trivial examples and let them play.
If you really want to tinker with that old technology, why don't you start out right by making it useful? Install Linux on it. It's too slow for Android, but you could try Firefox OS on it. Then you wouldn't be wasting your time learning an api for a dead OS.
It sounds like you're using the GPU as a DSP. Why not just get an embedded processor with a built in DSP? An example of an older generation one is the Atmel at9g45m. This is an older ARM core processor which has more power than you would expect. You can probably get away with using a fanless ARM system for your application. You may even find one that has enough processing power which doesn't even need a heatsink.
What can you do in Slackware that is impossible in Ubuntu?
In Slackware, you learn how to do things on any Linux distro. In Ubuntu, you only learn how to do things in Ubuntu, Debian, and Debian derivatives. I owe to Slackware the fact that I can sit down and work with any Linux distro out there. It doesn't include its own special tools for anything, so you are forced to do everything the "standard Linux way," which is the way that works on every distro (with some special exceptions, like DSL).
I would teach them basic bash scripting, and about /proc and /sys. Then I would have them write scripts to automate extracting information from /proc and /sys in bash using grep, sed and maybe awk. Teaching them how to work with Linux from the shell and how to pull information out of the kernel like this should give them some good insights into the operating system and its tools.
Additionally, I would teach them how to write init scripts and how to do "fun" things to get them excited about Linux.
I had the same dilemma, except I also knew I would eventually add 3D graphics as well. I wanted it to be portable to anything, and I needed it to render accurately and with proper anti-aliasing (anti-aliased while drawing, not via a filter after the fact). After mulling over all the options, I came to a difficult conclusion: write it myself. This is more work than I'd like, but it allows me to ensure it will run on anything, anywhere. If something new comes out that I want it to run on, I just port to it; I don't have to beg a vendor for it to be ported for me. Performance isn't paramount to my application, so I can put enough abstraction layers in to make the porting process relatively easy. All frameworks seem to put performance as the highest priority, which gets rid of the ease of portability. If your application will render graphics that sit still most of the time, this may be your best option (assuming you know linear algebra if you want vector graphics, and know graphics programming regardless).
This option worked for me.
You'll find getting back into the field, to program in high level languages with all of your previous experience outdated, to be very difficult. Companies will not want to pay you the salary your years of experience would warrant, and it would be like starting over.
Instead, the method back in that I've found for those of us who started in the "old days" is to go for embedded systems development. The embedded world uses 10+ year old technologies, so your experience with assembly language programming and writing software for systems with limited amounts of RAM and storage space is a big plus for embedded systems development. There are plenty of companies still creating software for processors that run at between 4 and 20 MHz with anywhere from 256 bytes of RAM on up to a handful of kilobytes of RAM. I've found this sort of development work is much more interesting, anyway, and people with old school knowledge are considered more valuable, rather than a dinosaur, for such work.
For such an expensive rocket launch, you'd think they'd at least have a professional photographer with professional lenses. Those pictures are terrible. Look at the flames; there's no detail. They obviously used cheap lenses. I'm an amateur photographer, but I have professional equipment because I'm too picky to have my pictures look as bad as their launch pictures do. I'm glad the launch succeeded, but you'd think they'd want better pictures for examining the launch and for PR.
He apparently wants us to take a step backwards to the days when crashes were frequent, such as with Windows 98. Software quality has a long way to go already. Does he not realize that making programmers deal with such an issue would bring software quality back into the Dark Ages?
As it is, programmers aren't given enough time to write software that works bug-free. Schedules are always rushed. This would dramatically increase: the burden on developers, the quantity of bugs, the number of developers being fired because they didn't get a project accomplished nearly as quickly as someone who pulled off a similar project 5 years earlier, the frustration of the users and developers (and transitively, the number of heart attacks around the world due to elevated blood pressure), the number of security vulnerabilities in software, and the migration rate to processor vendors who didn't make this mistake.
In short: this guy is on crack!
You're crazy!
The solution to this is simple:
1. Make sure you have an Enterprise licensed AV installed. The per-client cost is low, and the updates will be centrally managed by the server. If your network is too small for this to be cost effective, then just have Norton AV (or your favorite respected AV) on every machine in the network.
2. Don't give your employees local admin privs. This one change has, in my experience, made all the difference in the world for many small businesses.
This is much cheaper than paying the labor for having an IT person come in and clean up all the messes.
It's call Norton Ghost.
I don't know about you, but I don't want to be anywhere a nuclear reactor that Bill Gates had any part in designing. It's bad enough that computers running software he had a hand in creating have orders of magnitude more problems than software from any other source. Put Bill Gates into the nuclear reactor business, and... well, I shudder to think of the sheer magnitude of the potential for disaster there.
I go with ext3 for this personally. NTFS doesn't store *nix style filesystem permissions, and causes various other issues with you Linux systems. With ext3, you can store all your files with all of your permissions intact, the filesystem is mature and trustworthy, and you can still access all of the files from any operating system by simply connecting the drives to a dedicated fileserver machine (an older computer or small device works perfectly for this). Simply share your files via NFS, Samba and ftp (if you need ftp access for something like xmbc). Having a dedicated machine for this means you can also script your replication to the secondary drive, so that you only have to attach the drive for the mirroring process to take place.
This is the solution I've been using for about four years now, and it works great for me.
Featuring racing electrons?
;)
btw, first post!
"Second... I don't want my tax dollars being used for a mirror server."
You sound like a Microsoft junkie. I suppose you think opensource is, "evil evil bad!"?
That's easy! Switch them to Linux, where the devs weren't too shortsighted to realize that it would be a good idea to make everything on the desktop scalable. I run at my native resolution, which would make things a bit small for me, but all I have to do is set the monitor DPI to a higher value than actual, and everything appears at a nice, easily readable size.
How about a Mac Mini with a remote control? They have good audio hardware, you can connect it to your network wirelessly, and you can use Mac OS X, Linux or Windows on it for playing audio. They're also small, nearly silent, and women think they're cute.
Debian Minimal is what you're looking for.
Gee, THANKS Captain Obvious! I don't know what we'd do without you!
No pictures? How can they not show us any pictures of this? And why a joystick? Why not something more like a brainwave scanner? That way, when you're talking on the cellphone, and you get distracted by picturing what the person on the other end is saying, you crash into a wall! That would be so cool!
This is why I only ask musicians who are good at what they do for advice on audio equipment. If you want to know what's good, you have to ask a musician who's passionate about music. Musicians know what the music is supposed to sound like because they've spent countless hours learning songs and practicing their craft. By listening to them, I have a setup that's so good it's made me turn and look behind me more than a few times because I swore the noise was made by something in the room.
KRK Rokit Studio monitors with a BBE Sonic Maximizer, in case you're wondering.
My Direct Loans are still around 3%. I wonder why he's paying 8.5%.