Hacker News new | past | comments | ask | show | jobs | submit | sheffield's comments login

"How about ability to resize windows from all edges of the window. That alone is worth the 30 bucks."

That made me smile...


Love that you can hold option while resizing to change the size from the opposite ends. Very handy.


Or hold shift to keep the width/height ratio the same.


Ahh, very nice! It's crazy to think how many of these little touches are hidden in OS X.


Public transportation would be faster, more effective and comfortable then cars if more people used it.


I disagree. In Switzerland they have some of the best public transport in the world and I still tend to chose car fairly often. Public transport has the advantage that you can do something (e.g. watch movies, read books, etc.) while traveling while in a car that time is thrown in the trash.

But the problem is that public transport goes near where lots of people want to go but doesn't go where any person actually wants to go. This means further traveling time after the public transport bit is finished. And probably connections as well. This means, for me, that public transport takes about twice as long to get anywhere.

In my opinion the future is robot controlled cars. All the benefit of public transport with none of the inefficiencies, etc. Public transport is just an intermediate step.


The best thing about public transport in cities is that you don't need parking space. Hunting for parking space can easily take more time than you save by getting directly to your destination, and public parking can be quite expensive.

That said, many offices have reserved parking, which fixes this - though that real estate is valuable.


Well if my idea comes to fruition the automatic car service would only need parking for "overflow" cars when not in use. Some percentage of the system would always be in use so the cars would only not be in use when they were being repaired/upgraded/whatever.


It's a chicken-and-egg problem, for sure.


They list their sources at the bottom of the page.


Let's call it the Gathering of the New Herd!


I was thinking "Hacking Hurd for GNUmanity" as a play on "Habitat for Humanity".


Rivalry is always good, it's essential for evolution.


Let's see, we have FreeBSD, NetBSD, OpenBSD, and Solaris. Two of them have even been integrated in current GNU systems (Debian/FreeBSD and Nexenta). How does yet another kernel help?


Hurd isn't stuck in the seventies and aims to do more than re-implement a 40-year-old design.


The irony of this remark is that while it is literally correct, the truth of the matter is that Hurd is stuck in the early 90s and aims to re-implement a 20-year-old design.


... while wrapping it to make it look like an early 1970s design.


Or we all can just stick with Windows XP. Wouldn't it be great?


By Ayn Rand.

http://en.wikiquote.org/wiki/Ayn_Rand


"HTML 5" features like

    <input type="text" x-webkit-speech>
surely won't work.


Microsoft had their Windows SpeechAPI available in IE, like what, 5.0?

    var a = new ActiveXObject("SAPI.SpVoice");
It can do TTS and Voice Recognition, locally

And don't forget MIDI and Drect3D support was introduced in IE4. Before SVG, there was a trend of VRML in the industry and VML was added to IE.

And don't forget, the very first AJAX as made possible by the IE xmlhttp object.

TIME+dHTML was cool before Flash, even before these Web2.0 and HTML5 cool kids start yammering around.

And then Microsoft killed these features with their Silverlight.


>IE xmlhttp

MSXML XMLHTTP. MSXML 2.0 released with IE5 was first to support it. It got copied first by Mozilla, BTW, then as AJAX caught on in 2004 Safari copied it too.


The emphasis was in webkit.


Features that haven't been standardized are put in their own namespaces. For example, webkit-* and mozilla-* had conflicting implementations of CSS gradients for a while. After the standard was ratified, the prefix was removed. Safari still supported the old webkit-* syntax, and Firefox still didn't, just like before, but new pages could use the functionality without the prefix and it would work in both browsers.

Also, if webkit has settings or features that are specific to the library used, it makes sense to put those in a different namespace as well, to avoid pollution.


What is wrong with that? It's a vendor extension, like most new CSS and JS features are implemented. A draft specification for the Speech API exists since last October, if I'm not mistaken. So why would that not work?


Most will fail gracefully though. For example that one will just render as a normal text input on older browsers.


But in English it is. It's acceptable to develop faster for certain (popular) languages.


Absolutely, but I would be surprised if they didn't have some code in the production version right now to support doubtlessly upcoming translated versions - perhaps not a full blown declension engine, but it seems unlikely they'd go English only at the start and retrofit everything later. The code might not be optimized to just let them do a simple find/replace for English.


The problem of translation should not affect the writing of the original text.


For all you know, the "original text" is a mix of "foo bar" and lolspeak.


I think the moral of this story is that it's not your business. She will decide what she want to do, and her parents should help, and not restrain her, or tell her what to do.


The time served might be much less then the sentence.


Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: