shaan7

21 ms·

181.
by shaan7 6y ago
Finally someone seems to have done this right. Subscribed now, lets see how it goes!
182.
by shaan7 6y ago
> There's no clear-cut rule here Exactly, that is why it is important to follow standards. Most engineering decisions are not clear-cut and are born out of tradeoffs. That is why we agree on standards that define those tradeoffs ins
183.
by shaan7 6y ago
Ah I think I did not describe the repercussions of making exceptions (even if they are in highly specialized cases like this). If you allow yourself to make such exceptions, you diminish the motivation for you (or someone else) to fix the p
184.
by shaan7 6y ago
> And honestly the practicalities of this situation and the risk-reward tradeoff seriously tilts toward repeating the request later regardless of what the RFC says. The world isn't going to end. That is exactly the thought process t
185.
by shaan7 6y ago
Did you mean to comment on https://news.ycombinator.com/item?id=25344762 instead ? xD
186.
by shaan7 6y ago
True for snap but not for flatpak
187.
by shaan7 6y ago
> Why do you think it gets repeated by Go developers? Not by all, only by a subset of Go developers (until very recently I was one as well, maintained a moderate-size webservice). I specifically said "some Go developers" in my
188.
by shaan7 6y ago
> So your programming languages of choice should base on your team. While that is a good thing to keep in mind when making tech decisions, make sure not tunnel vision only on it. More about that here https://news.ycombinator.c
189.
by shaan7 6y ago
What higerorderma said above applies to this ^ comment as well. It is another of those nonsensical things that keeps getting repeated all the time by some Go programmers. That line of thinking promotes workarounds over long-term solutions.
190.
by shaan7 6y ago
Although I get your point, there is an important difference between those two though. Once you've bought the CD you can listen to it forever, that is not true for subscriptions - _that_ is why they are cheaper. I kinda use a hybrid - I
191.
by shaan7 6y ago
Thank you for recording these <3
192.
by shaan7 6y ago
> how proficient your team is in a given language and how easy it will be to maintain afterwards that are simply more important. That is a double-edged sword. On one hand it makes sense because it allows teams to be more productive. Otoh
193.
by shaan7 6y ago
Yep that is the beauty of having alternatives :) Ideally I'd have a DE which is polished and has features that I need. Unfortunately there's nothing (macOS, Windows included) that does both, so we choose our poison.
194.
by shaan7 6y ago
> People love to criticize Apple, but man do they do some wonderful things for their customers. People rarely criticize Apple for the products themselves. Apple gets criticism because of the "weird" (for lack of a better word)
195.
by shaan7 6y ago
> support for peripherals and common communication/presentation software is really lacking Well if peripherals vendor and "common communication/presentation software" didn't test on Linux, whose drawback is it no
196.
by shaan7 6y ago
Combine that with the needs of designers to "make the experience unique" to a level where consistency goes out of the window. Every commercial software these days has its own idea of design and it gets irritatingly hard to learn a
197.
by shaan7 6y ago
Well, nice to know that I'm not the only one who feels this way. Both you and tomc1985 are correct - it is this weird human thing where most people will continue to do things knowing full well of the consequences. For example we know
198.
by shaan7 6y ago
Maybe it depends on the peers near you and when you watch. I tried to play a video on the OP's website, it played immediately at 1080p without any stutter.
199.
by shaan7 6y ago
Wait, it is possible to get a genuine* battery replacement for an Apple device? And no, I'm not being sarcastic, my friend was told by an Apple Store that even an attempt to open the Macbook chassis voids warranty. They refused to rep
200.
by shaan7 6y ago
> devices on two criteria: 1) price, 2) UX/familiarity Interesting. Won't you agree that before 1 and 2 there is an implied 0 - must be Android or iOS (so that it can run Uber, Amazon etc)? EDIT: maybe you misunderstood when I
201.
by shaan7 6y ago
Ah ok. Well then Android is the only thing that'll satisfy that criteria. It is going to be _impossible_ for anything else to compete with iOS/Android because of the app ecosystem catch-22. Apps area the primary criteria that cons
202.
by shaan7 6y ago
> As I've repeated many times here, now, though, I'd love to see more platforms compete with iOS. Not with the app store. With iOS and its overall ecosystem. Isn't that a contradiction? App Store _IS_ "its overall eco
203.
by shaan7 6y ago
> what I'd call a standard Um, just calling a monopoly a "standard" doesn't make it so. There are already standards for the the web that are defined by the W3C. It is a win for a standard if there are multiple impleme
204.
by shaan7 6y ago
That keyboard reminds me of the Nokia N900 <3
205.
by shaan7 6y ago
Thanks Ben!
206.
by shaan7 6y ago
> For example, new features arrive for all platforms at the same time That (and everything else you said) is true for any cross-platform framework, not just Electron.
207.
by shaan7 6y ago
> without writing everything in C++ That sounds interesting. Can you list the major technical reasons behind this decision? Also interesting will be if you could explain how Rust addressed those pain points (I have read about the general
208.
by shaan7 6y ago
> Why shouldn't it be Electron? Because every Electron app is inconsistent with the rest of the desktop. I use a dark theme system-wide but Electron won't care [edit: 1Password has custom integration for GTK theme]. Honestly, t
209.
by shaan7 6y ago
> state of the art in nowadays OSS I agree with that, in fact it has been for quite a while. There are lots of OSS projects which have companies selling proprietary extensions for. For example, The Qt Company sells a proprietary plugin t
210.
by shaan7 6y ago
Exactly. I always knew about VSCodium but was lazy. This article (thank you!) made me stop procrastinating. I have replaced VSCode with VSCodium now.

More ›