atinoda-kestrel

6 ms·

1.
by atinoda-kestrel 11y ago
>That's not entirely true. The MeeGo org was a mess. Obviously you have an inside perspective that I don't, but from the outside it just looked like y'all made an amazing phone. :) I can't say I heard much about inte
2.
by atinoda-kestrel 11y ago
> They built tablets and phones that were very interesting for people who want to add Debian repos to their phone. Did you ever use an N9? It was nothing like that. The 770 tablet, and such, sure. But the N9 was quite far removed from
3.
by atinoda-kestrel 11y ago
> Then the phone market changed, it became a battle of software. Nokia wasn't a software company, they didn't understand this new market and culturally couldn't deal with the changed market. By the time they realized this
4.
by atinoda-kestrel 11y ago
They're not done yet. But they've slowed the bleeding tremendously, gotten out of unprofitable businesses, actually shipped the damn OS (instead of farting around with demos and research), and are working to ensure that QNX provi
5.
by atinoda-kestrel 11y ago
Oh he does. Just only while the VCs are writing checks. ;)
6.
by atinoda-kestrel 11y ago
> There're way too many developers who read links from HN and try and push the javascript framework of the weak on everyone at their job without fully comprehending the consequences of their decision. One good question to ask yours
7.
by atinoda-kestrel 11y ago
FOSS != GPL. I've written plenty of stuff under the BSD license which has been distributed with and without modifications in tons of commercial products, rarely with source. Totally fine, and exactly as I intended.
8.
by atinoda-kestrel 11y ago
> What's the advantage of that as opposed to the 'standard' java way of doing immutable via 'final'? They're not really comparable. This is code generation for builders, getters, etc. The idea is that you
9.
by atinoda-kestrel 11y ago
> Wasn't that Blackberry's line? Yes, and years later BlackBerry is still around, with a CEO that's almost finished reversing the damage the previous ones caused. I get your point, but still. Also, you seem to be conflati
10.
by atinoda-kestrel 11y ago
Oh, I think the idea is plenty neat. It's how it's ended up in JS that I'm not a fan of.
11.
by atinoda-kestrel 11y ago
I wasn't responding to the parent poster directly, but rather addressing some comments I've heard in meatspace. Sorry I didn't make that clear!
12.
by atinoda-kestrel 11y ago
> 1. why did you get out of the file host business or why were you glad to? Handling abuse complaints, wrangling bandwidth spikes, etc. ended up taking way more time than I wanted to give to it. This was before a lot of the modern eas
13.
by atinoda-kestrel 11y ago
> I find most people who have gripes with JS prototypes are the ones who are used to classical inheritance. Counterpoint: Scheme/Lisp/FP fans also don't tend to like it. Myself included.
14.
by atinoda-kestrel 11y ago
> Are there any index funds that track the entire market? Wouldn’t investing in all companies solve the problem of index tracking? Yes, there are funds that try to match the entire market. Vanguard runs a couple "total market&quot
15.
by atinoda-kestrel 11y ago
> Nicotine is directly harmful to your heart. Yes, but it's worth noting that the increased risk of heart disease from smoking is due to more than just nicotine.
16.
by atinoda-kestrel 11y ago
A long time ago I ran a file hosting service that almost exclusively served one particular "fringe" community (for some reason it got really popular on one site and spread from there). I was running it anonymously at the time (
17.
by atinoda-kestrel 11y ago
> So you still need tools and tools programmers. You might not have an entire team building an editor, but you need something (and it's very easy to build custom editor tools inside the Unity editor). No disagreement there. I just
18.
by atinoda-kestrel 11y ago
> I think that game studios have the right model: Hire full-time tools engineers and task them with making the tool-users more effective. That's one approach, but it's not always the right one. It's only really necessary
19.
by atinoda-kestrel 11y ago
Which one is snake oil again? Well... cod liver oil, actually. And that would be here: http://store.chriskresser.com/ Frankly, I wouldn't put a whole lot of faith in either.
20.
by atinoda-kestrel 11y ago
Great response! There's also the lovely condescension that I can't help but sense when someone tells me why writing code every day shouldn't be as fulfilling as it is. That's a big part of how some people get a sense of
21.
by atinoda-kestrel 11y ago
For me the big win with 80 is that I can easily do a side-by-side diff in my IDE without needing to expand the diff window at the expense of the outline, package, and other views. And horizontal scrolling in a diff view sucks. A lot.
22.
by atinoda-kestrel 11y ago
There's a middle ground though. On my team, the long-standing rule is that you need to make a best effort to stick to the module's existing style. So we're not gonna bust your balls because you don't split at exactly 10
23.
by atinoda-kestrel 11y ago
Yeah, I'm not sold on "fewer characters" as a win. 'cause then we can have the code golf arguments that inevitably get into the nutty realm. For visual parsing, consistency matters. In an object literal dec I expect:
24.
by atinoda-kestrel 11y ago
Hmmm... I wonder if there's potential to use this concept for video. Not this implementation, naturally, but the concept. I'm a little too sleep deprived to think through this entirely, but just off the top of my head, it seems l