iterati

10 ms·

61.
by iterati 8y ago
As someone who worked as a software engineer in NYC for 6 years ~5 years ago, I couldn't disagree more strongly with your claim that the tech scene in NY is weak. It's second only to Silicon Valley when it comes to tech jobs.
62.
by iterati 8y ago
I don't think it's reasonable to think that most people working at HQ2 would have been doing a reverse commute from Manhattan into LIC. It's equally likely that they would just be crowding the already crowded trains heading t
63.
by iterati 8y ago
> The subway for people commuting into LIC for work is probably currently fairly empty, so the subway could accommodate them. (The same cannot be said of the reverse. Commuting from Astoria, Queens or Williamsburg, Brooklyn into Manhatta
64.
by iterati 8y ago
as-> is great for when you have to mix thread-first and thread-last. cond-> is great for building maps where some keys might not be needed: (cond-> {:k1 v1} v2 (assoc :k2 v2) ...) some-> and some->> I
65.
by iterati 8y ago
User isn't the same as customer, though. Evernote needs customers. They only have users.
66.
by iterati 9y ago
This is actually why I love working in Clojure. There are a number of threading macros to make this pipeline stuff work in different scenarios (put the return value in as the first, last, or variable argument; stop and return nil if you eve
67.
by iterati 9y ago
I played clash for 18 months. You even say yourself that it's p2w: > (3) the 1v1 ladder is not a pure skill matchup but still finds everyone a range where they have essentially a 50% win rate based on a combination of progress and s
68.
by iterati 9y ago
They'd be fired.
69.
by iterati 9y ago
I guess we will, but with the slow pace that any of this was (not) done over the last number of years, I'm not holding my breath.
70.
by iterati 9y ago
> They lost me once for terrible, terrible performance. For a year or two until I really needed tree style tabs back. They need to prioritize. Deal with it. I am dealing with it. I moved to a different browser. > Also, since you'
71.
by iterati 9y ago
> I've developed a couple of Firefox extensions. One of those was an e10s-compatible replacement for Vimperator, because Vimperator relied on XUL[0]. Replacement for Vimperator implies it's, well, a replacement for Vimperator.
72.
by iterati 9y ago
electrovim is in no way a replacement for Vimperator. It's a couple of keyboard shortcuts. None of the current vim-like plugins for FF57 match what vimperator/pentadactyl can do. The problem I have isn't that they broke legac
73.
by iterati 9y ago
In the mean time, they've lost one of those power users (likely more, going by some of the discussion in issues for various vim-like plugins) and will, in the future, need to do something to entice me back. This experience has left a b
74.
by iterati 9y ago
Simply false. You don't appear to know what you're talking about, so maybe you should stop pretending. https://bugzilla.mozilla.org/show_bug.cgi?id=1215061
75.
by iterati 9y ago
Doesn't matter how technical it is, it's still pretty worthless.
76.
by iterati 9y ago
The right thing to do would have been to work on those extensions BEFORE breaking users' experience.
77.
by iterati 9y ago
You don't break something and then prioritize fixing it. That's backwards. If they knew it was going to break the proper thing to do it prioritize the fixes before it effects end users, not after. If I were to push up a breaking c
78.
by iterati 9y ago
It's not too soon to judge - plugins I used no longer work unless I turn off auto-update or move to the LTS version. The team knew these were breaking changes for months or years, but the APIs to un-break things don't exist and ar
79.
by iterati 9y ago
Less "dire warnings on forums" and more "slow development pace for required pieces to make my workflow even possible again". Here's an issue opened June 9 that hasn't been addressed by the Mozilla team and hasn
80.
by iterati 9y ago
That's the issue - there's no real path to making these legacy plugins work. There are open issues for a keyboard api for FF that has had very little movement over months, so while I'm sure it'll eventually get to a poin
81.
by iterati 9y ago
I've tried Tridactyl, but the plugin not working on Firefox pages is the same frustration I had with vim plugins for Chrome.
82.
by iterati 9y ago
If the vim stuff was the only plugin I needed, I'd move over in a heartbeat.
83.
by iterati 9y ago
This is sadly true. I switched off Chrome 5+ years ago due to the "vim-like" plugins being much better on FF than Chrome (specifically, my keybindings not working on built-in pages) and since FF56, vimperator and pentadactly no lo
84.
by iterati 9y ago
So use @property then?
85.
by iterati 9y ago
I was lucky enough to land a Clojure job (stitchdata.com, we're hiring!) before having to learn Clojure, because I had the benefit of experienced mentors helping me get to grips with lisps (which were alien to me) and a development wor
86.
by iterati 11y ago
Who needs privacy when you have nothing to hide?
87.
by iterati 11y ago
Yes, my level of respect for traders is exactly zero. There's a difference between investing and trying to make a profit off short-term trades, arbitrage, and other forms of financial practices that offer dubious value to anyone other
88.
by iterati 11y ago
The transit alerts for NYC are pretty brain dead. I get alerts at lunch alerting me that my commute home has service disruptions on the subway. I'm not leaving for 6+ hours so the notifications are useless.
89.
by iterati 11y ago
> To summarize, Mel enabled the index register bit (despite not using the index register) to cause an integer overflow, and because the instruction was at the very top of memory, it had the side-effect of also incrementing the instructio
90.
by iterati 11y ago
If your first inclination in marketing your project is to make it a terrible pun instead of something more descriptive and correct, you're doing it wrong.

More ›