The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I am still happily using my Blackberry. It and it's predecessors have never failed me and the touch screen it doesn't have can be cleaned without making long distance phone calls or deleting all my notes and contacts - you really have to watch what you swipe on an iCrap! I also have a couple of hundred books loaded on it that I am working my way though - very easy to read on the high-enough definition screen. I also use a wonderful (free) app called Google Maps that unlike that fruity version actually seems to know where it is and how to get elsewhere accurately.
I use Tether or a USB to connect to the internet via my PC (Bluetooth definitely is switched OFF) or simply use my 4G through AT&T - which is VERY fast!
My plan gives me unlimited everything (grandfathered in) for one fixed fee.
I love my Blackberry and drink (imported) Ribena (at $12 per litre - concentrated though) to celebrate it every day!
- Life in the fast lane is only fun if you live in a country with no speed limits.
- Of all the things I have lost, it is my mind that I miss the most.
- I vaguely remember having a good memory...
When I delete a file from within an application (say, Visual Studio) rather than from Explorer, wouldn't it make more sense for that file to be sent to the recycle bin (rather than be deleted forever)?
I'd say this should be the default behavior, but there are instances where that wouldn't be desired (e.g., an application that continuously creates temp files then deletes them when done with some processing... that'd fill up the recycle bin pretty fast). Maybe a second recycle bin for application-initiated deletes would work (one with its own capacity and "overflow" policy)?
I know we can explicitly code for files to be sent to the recycle bin, but it's almost never done, so I'm thinking doing this by default would be the ideal solution. Perhaps they'll add this to Windows 9 or .Net Framework 5.
Perhaps they'll add this to Windows 9 or .Net Framework 5.
And if they added this to .Net Framework 5, someone will post:
I know we can explicitly code for files to be deleted permanently, but it's almost never done, so I'm thinking doing this by default would be the ideal solution. Perhaps they'll add this to Windows 10 or .Net Framework 5.5.
So, I think it's the best idea if a programmer is required to pass a moveToRecycleBin boolean or something like that.
Whilst hanging innumerable Christmas lights at my lady's house this weekend (and last) it occurred to me that there is nothing stopping us from creating wire strings that contain individually-addressable lights LEDs, with a wireless controller at the power plug. IPv6 makes a virtually unlimited number of addresses available, so it's quite feasible from an addressing standpoint. Think of the fun you could have writing programs to animate the yard display, without having the deal with a bunch of electromechanical relays and such that are traditionally employed by the lunatics who make an annoying, animated display of their yards every year. Not only would it save electricity, but it would also open up a whole new field of application programming for you all!
So, why isn't it already being done? What's holding us back?