Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shutter
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
91.
▲
by
shutter
18y ago
I'd settle for a laptop that tells my coffeepot to make coffee.
92.
▲
by
shutter
18y ago
That's authentication/authorization info; it should/must be stored on the client.
93.
▲
by
shutter
18y ago
Eh, Stephen Hawking seems to be doing OK.
94.
▲
by
shutter
18y ago
That looks just about perfect . Too bad I don't have the min. # of daily active users yet (20,000). Edit: I might be able to hold out on this for now and just use that when it becomes available. Looks very promising.
95.
▲
Should I use XMPP for my startup's messaging system?
12 points
by
shutter
18y ago
|
13 comments
96.
▲
by
shutter
18y ago
They had to -- they wouldn't be virgin galactic anymore.
97.
▲
by
shutter
18y ago
It's usually better to get something out sooner. You can always go back and "tweak" IE if you have time. Companies can thrive on less than 100% of the market; look at Apple as one example. You don't have to win everyone over to succeed --
98.
▲
by
shutter
18y ago
Few organizations have higher uptime requirements and so much money (literally) at stake... I'd imagine that it'd be tough to push through any kind of software/system change, let alone large-scale ones. (If it ain't broke, don't fix it.) Th
99.
▲
by
shutter
18y ago
Unrelated: I am amazed that this page is now #1 on that Google search you linked to. Less than an hour, post to index? That's fast.
100.
▲
by
shutter
18y ago
Wholeheartedly second this question. I've always enjoyed software, but I have an itch to play with hardware too.
101.
▲
by
shutter
18y ago
Most typical users don't care about URLs, and many people don't know the difference between typing a URL into their address bar or typing a search term to get them there. (IMHO, that's an unfortunate truth.) The primary problem with that tr
102.
▲
by
shutter
18y ago
Just come right out and say it -- show them advice from agile developers (37Signals, etc) that says "get your stuff out the door or you may not succeed". Architecture can be flexible -- applications will evolve with growth. As noodle said,
103.
▲
by
shutter
18y ago
Couldn't agree more.
104.
▲
Economies of Scale (Roy Fielding)
(roy.gbiv.com)
3 points
by
shutter
18y ago
|
0 comments
105.
▲
by
shutter
18y ago
Written a dozen years ago, yet still interesting. I often wish I had taken a bigger interest in math, because AI really, really intrigues me. I'm finishing up a CS degree, but that hasn't stopped me from thinking how it'd be interesting w
106.
▲
by
shutter
18y ago
Developers don't want to have to develop for multiple platforms. There are two ways to solve that: Either develop for a platform which has a monopoly share, or develop cross-platform. Web Applications' ability to work on every platform, com
107.
▲
by
shutter
18y ago
Scaling something to 10K isn't easy no matter what system you use. Erlang isn't a silver bullet.
108.
▲
by
shutter
18y ago
I have a question related to this: I've heard a little about issues like this, where old data still exists even though you thought you deleted it -- or it's still in RAM for instance. When I read TrueCrypt's info, I seem to recall something
109.
▲
by
shutter
18y ago
Blocking IE7 is overboard. If the browser is your platform , I'd forgive blocking IE6. If you're selling a desktop application , blocking IE6 or IE7 doesn't make financial sense.
110.
▲
by
shutter
18y ago
I think that the reason we don't see decreases in bloat is because developers generally don't want to remove features once a program has been released. Instead, they strip things down and re-release it as a new , leaner product. Then t
111.
▲
by
shutter
18y ago
What do you mean when you say "keep the SMTP operations separate from the web application"? With a queue?
112.
▲
Ask HN: Pointless Spam?
25 points
by
shutter
18y ago
|
20 comments
113.
▲
by
shutter
18y ago
I almost didn't give yellowing a second thought on old devices, since I saw the same effect on all types of old paper (especially newspapers).
114.
▲
Paper tigers and hidden dragons (by Roy Fielding)
(roy.gbiv.com)
3 points
by
shutter
18y ago
|
0 comments
115.
▲
by
shutter
18y ago
The CSS should go in the head, and the Javascript can be placed at the very end of the page right before the closing body tag. Failing that, you can put the JS right below the CSS in the head tag.
116.
▲
by
shutter
18y ago
Be a better platform.
117.
▲
by
shutter
18y ago
Finally, an intriguing glimpse of what the web could become in the future, if we open ourselves up to the possibilities. I didn't see anything in that video that was "way out there" either. With enough foresight and vision, something like
118.
▲
by
shutter
18y ago
The "Beyond REST" moniker is a little propaganda-ish. REST has its place and is a great architectural paradigm. Apart from that, the slideshow was pretty useful and informative. For me, it couldn't have come at a better time -- it pointed o
119.
▲
by
shutter
18y ago
If the charge was _minimal_, I'd be willing to pay a few bucks a year for Facebook. If you use it properly (read: non-obsessively), it's a great way to keep connected with people you've known in the past several years. Without Facebook, I w
120.
▲
by
shutter
18y ago
I'm not really a "Mac" developer, since I don't (yet) code for the Mac APIs, but I'll respond anyway: I primarily code in Python and Javascript, but also some C/C++ non-GUI stuff. I tried a few different cross-platform Python IDEs, but nowa
More ›