|
title: Put the knife down and take a green herb, dude. |
descrip: One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com Using 89% of the same design the blog had in 2001. |
|
x
MarkUpDown is the best Markdown editor for professionals on Windows 10. It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support. Features you won't find anywhere else include...
You've wasted more than $15 of your time looking for a great Markdown editor. Stop looking. MarkUpDown is the app you're looking for. Learn more or head over to the 'Store now! |
|
| Friday, August 30, 2013 | |
|
Why the Nintendo 2DS Makes Sense: It's Not For Gamers | Will Greenwald | PCMag.com: The 2DS is cheaper because it lacks that hinge and includes the ability to build the two "screens" on the 2DS with one LCD panel and a plastic bezel. The cost of manufacturing the 2DS with a single LCD panel and a single enclosure is certainly less than the cost of building a device with two LCDs (one with glasses-free 3D) and two enclosures connected by a hinge. Kinda embarrassed I didn't immediately figure that out myself. Clever girl. Edit: I'm also surprised with all the press saying this is a highly targeted design for young kids to stick in their backpacks rather than their pockets, and won't have more universal appeal. As if the iPad suffers for not having a "clamshell" design. (The original iBook; that had a clamshell. Anyhow...) My DS usually sits on my desk. What do I really care if it's essentially a tablet? This, my friends, is a great example of a minimally viable product. No 3D, no folding, no stereo speakers, just mono. Who cares? If I didn't already have access to a 3DS, A Link Between Worlds would probably have me shelling out for a 2DS this holiday season. Labels: nintendo posted by ruffin at 8/30/2013 06:31:00 AM |
|
| 0 comments | |
| Tuesday, August 27, 2013 | |
|
No Henry, you need to get real about Yahoo. Here are the facts — Tech News and Analysis: And forget the products — so far Yahoo has been unable to attract top quality talent to the company. Not one 20-something I have talked to in the past six months has wistfully talked about working for Yahoo. And even those who have joined Yahoo from Google are joining the company thanks to mega-million dollar contracts, not because they want to work there. When Yahoo becomes the desired job-spot for a fresh, new tech tinkerer — that will be the time I will lighten up on Yahoo. I think the folks at my current company would benefit from having similar goals as Malik's for Yahoo. Having not just lots of folks, but the right types of folks wanting to work with you is the best sort of flattery. More posts based on links shared by Gruber. Glad I went off the "articles only" feed to the busier one. posted by ruffin at 8/27/2013 09:11:00 PM |
|
| 0 comments | |
|
Microsoft's Ballmer: Why Microsoft doesn't want to be IBM (or Apple) and more | ZDNet: Apple is trying to make a lot of money on the device. Amazon is trying to make it all on the back-end. So is Google. Rather than say the model is FOO or BAR, the model is to deliver these incredible, high value experiences that will span hardware innovation, operating system, consumer experiences and enterprise experiences... For all the dislike I have for Ballmer's contribution to M$'s Profit Maximization Machine, there's a part of me that knows, on some technical level if nothing else, he really gets it. Labels: microsoft posted by ruffin at 8/27/2013 08:36:00 PM |
|
| 0 comments | |
| Friday, August 23, 2013 | |
|
Gosh, I'm an idiot. Would have been nice to notice that button ("Show Command Line Popup") on the Script tab, well, YEARS AGO. posted by ruffin at 8/23/2013 09:35:00 AM |
|
| 0 comments | |
| Friday, August 16, 2013 | |
|
iTunes, App Store, iBookstore, and Mac App Store Affiliate Resources - Search API: Searching Wow. Really? It's that easy to turn music searches into 5% back? Why isn't everyone doing this, and why in the world is Banshee Amazon mp3 only? This is INSANELY easy. I know I sound like an infomercial dude here, but wow. I'm surprised I don't see iTunes store search widgets everywhere. Want five Black Crowes albums? https://itunes.apple.com/search?term=black+crowes&entity=album&limit=5 Hello, JSON: {
"resultCount": 5,
"results": [
{
"wrapperType": "collection",
"collectionType": "Album",
"artistId": 481547798,
"collectionId": 481547797,
"amgArtistId": 3688,
"artistName": "Black Crowes",
"collectionName":
"Stare It Cold (Recorded live at Greek Theatre, Nov. 1991 in L.A. CA, USA)",
"collectionCensoredName":
"Stare It Cold (Recorded live at Greek Theatre, Nov. 1991 in L.A. CA, USA)",
"artistViewUrl":
"https://itunes.apple.com/us/artist/black-crowes/id481547798?uo=4",
"collectionViewUrl":
"https://itunes.apple.com/us/album/stare-it-cold-recorded-live/id481547797?uo=4",
"artworkUrl60":
"http://a3.mzstatic.com/us/r1000/089/Music/09/30/87/mzi.osaekjzf.60x60-50.jpg",
"artworkUrl100":
"http://a5.mzstatic.com/us/r1000/089/Music/09/30/87/mzi.osaekjzf.100x100-75.jpg",
"collectionPrice": 10.99,
"collectionExplicitness": "notExplicit",
"trackCount": 11,
"copyright": "℗ 2011 Akarma",
"country": "USA",
"currency": "USD",
"releaseDate": "2011-09-20T07:00:00Z",
"primaryGenreName": "Rock"
},
{
"wrapperType": "collection",
"collectionType": "Album",
"artistId": 2969371,
"collectionId": 278116879,
"amgArtistId": 3688,
"artistName": "The Black Crowes",
"collectionName": "iTunes Originals: The Black Crowes",
"collectionCensoredName": "iTunes Originals: The Black Crowes",
"artistViewUrl":
"https://itunes.apple.com/us/artist/the-black-crowes/id2969371?uo=4",
"collectionViewUrl":
"https://itunes.apple.com/us/album/itunes-originals-black-crowes/id278116879?uo=4",
"artworkUrl60":
"http://a5.mzstatic.com/us/r1000/034/Music/62/91/e9/dj.bbvgvohe.60x60-50.jpg",
"artworkUrl100":
"http://a4.mzstatic.com/us/r1000/034/Music/62/91/e9/dj.bbvgvohe.100x100-75.jpg",
"collectionPrice": 9.99,
"collectionExplicitness": "notExplicit",
"trackCount": 27,
"copyright": "℗ 2008 Silver Arrow Records",
"country": "USA",
"currency": "USD",
"releaseDate": "2008-04-15T07:00:00Z",
"primaryGenreName": "Rock"
},
...
And that stuff works. Album link: https://itunes.apple.com/us/album/itunes-originals-black-crowes/id278116879?uo=4 Album image: Labels: iTunes, noteToSelf posted by ruffin at 8/16/2013 12:29:00 AM |
|
| 0 comments | |
| Thursday, August 15, 2013 | |
|
Thank you, Skitch, for making me opt-out of your running in the background, taking over Control-Shift-B system-wide, and making me think I'd somehow screwed up my settings to Build in Visual Studio. posted by ruffin at 8/15/2013 04:14:00 PM |
|
| 0 comments | |
| Sunday, August 11, 2013 | |
|
C# Error: Parent does not contain a constructor that takes 0 arguments - Stack Overflow: Constructors are not inherited in C#, you have to chain them manually. You'd think I'd've run into this issue this many years into using C#, but I hadn't. Object inheritance simply isn't as straightforward a process (as opposed a concept, as, conceptually, it's exactly the same) [for me] in C# as it is in Java. I don't know if that's because I learned Java first or if C# really is more convoluted. I'd like to pretend I'm 90% sure it's the latter, but will hold off being disappointed until I consider it a bit longer. As I used to think (and mentioned wrt an Eric Lippert SO post a little while back) that VB.NET was just a convenience layer on top of C#, I also used to think C# was Microsoft's version of their legacy code spun into a great Java clone. That belief is simply not the case, and I wonder why the differences that do exist do. What's the advantage of "manually chaining" constructors? Labels: c#, noteToSelf posted by ruffin at 8/11/2013 04:27:00 PM |
|
| 0 comments | |
| Wednesday, August 07, 2013 | |
|
Google under fire for Chrome browser's password storage policy: Responding to the controversy, the tech lead for Chrome's browser security team said that they had found that "boundaries within the OS user account [to protect passwords even when a user is logged in] just aren't reliable, and are mostly just theater." This mostly suggests that the tech lead for Chrome hasn't read Joel Spolsky's Let Me Go Back! strategy letter nor ever heard the saying, "A lock keeps an honest man honest." "But wait! Joel's not talking about security, you fool! He's talking about how Excel ate Lotus 123's lunch!" you say. That's right, but he's also talking about barriers to entry.
On this reread, "calculus" seems a bit strong, doesn't it? But this works with folks trying to read your passwords too. How many little sisters (or slightly seedy buddies) might have access to your browser? Um, lots. Better yet, how many high-end art thieves contribute to Dollar General's shrinkige issue? That'd be essentially none. Completely different "markets" for different sorts of exploits. More clearly: Folks that install apps on your computer to phone home to some nefarious server in Elbownia do not read your passwords from your settings page. They do whatever they want. Folks that visit your house might. Reportedly again from the Chrome tech lead: Consider the case of someone malicious getting access to your account. Said bad guy can dump all your session cookies, grab your history, install malicious extension to intercept all your browsing activity, or install OS user account level monitoring software. ... the conclusion we always come to is that we don't want to provide users with a false sense of security, and encourage risky behavior. Right, because most passwords stolen from the settings page is from "someone malicious getting access to your account." Your little sister is going to "dump your session" and "install malicious extension [sic] to intercept all your browsing activity" or, get this, "install OS user account level monitoring software." How many times have you seen someone doing this, ever? How many people do you know who could do this? The "market" described above is not the one that needs a master password. Get out of the ivory tower and back into your living room, Chrome, because that's where your users live. I'll posit that adding a barrier to entry probably does cut the number of passwords stolen in half. I'd like to see Google's study, not their tech lead's off-the-cuff impressions, suggesting otherwise. posted by ruffin at 8/07/2013 02:14:00 PM |
|
| 0 comments | |
|
jquery.workflow.js: I enjoy seeing unlocalized errors in languages other than English. I'm not saying it's right, but turnabout's fair play. Too often I "protect" a condition that "should never happen" with a quick English blurb -- I'm good about not doing that at work, as we have a pretty robust localization workflow, but the stuff I do "for myself" has a number of throw new Exception("Here's some Anglais pour vous"); examples -- and it's fun to see what that really means when it's put into context with something like this code. posted by ruffin at 8/07/2013 11:19:00 AM |
|
| 0 comments | |
| Friday, August 02, 2013 | |
|
.net - static/Shared in VB.NET and C# visibility - Stack Overflow: Remember, the design criteria of different languages are different, and therefore the decisions made are different. On the C# design team, we highly value a language definition which makes illegal patterns that look suspicious; since there's no meaning to passing an instance as the receiver to a static method (unless computing the receiver expression causes a side effect) then why allow the user to type meaningless code? Just horrendously interesting. Though I still feel a little like VB.NET is just a compatibility layer draped over C# in practice, at least in theory I'm starting to believe the difference is more nuanced. posted by ruffin at 8/02/2013 10:30:00 AM |
|
| 0 comments | |
|
|
All posts can be accessed here: Just the last year o' posts: |
|||||||||||||||||||||
|
||||||||||||||||||||||
|
|
|
|