HN user

iliaznk

183 karma

[ my public key: https://keybase.io/iliaznk; my proof: https://keybase.io/iliaznk/sigs/WrUmul2AGAStHWxC3x-Ra99nUYoDGQi2969Zwajq_DI ]

Posts3
Comments223
View on HN

I mean in a complex enough application you'll have to come up with some abstractions that will make you life easier anyway. I doubt that you will manually add and remove classes, or add and remove nodes via direct DOM API calls every time you need to do that. You know what I mean? A set of such abstractions is what I call a framework. It doesn't have to be a separate file called "framework.js". It may even be more of a library than a framework. But I believe you will inevitably come to that to centralize certain things and make them easier to do.

We have encountered that problem too. As far as I learnt from various sources that is caused by circular imports in some cases, and by using index files that re-export your modules in other.

Actually I don't think that Google makes any money from YT in Russia because they disabled ads for Russian users altogether about 2 years ago, and there's no easy way to pay for a premium subscription in Russia since SWIFT stopped working, unless there're other ways it can make money other than those two. And it's very good that they still keep working in Russia anyway, because it provides a platform for alternative views and opinions. As a Russian, I'm really glad we still have YT and surprised it hasn't been blocked.

An anecdote:

A reporter interviews an old highlander at his home:

- What's your secret? How did you manage to live for so long? - For all my life I've followed three simple rules: no alcohol, no tobacco and no women!

Suddenly they hear some noise behind the wall in the other room.

- What's that? - asks the reporter. - Oh, that's my elder brother. He's drunk again and is beating his wives for hiding his cigarettes.

Thanks for submission! Very timely. Been searching for a stable and flexible editor (or rather a tool to build such an editor) and Tiptap looks like a good candidate.

I was also considering Slate, but have found this rather annoying bug https://github.com/ianstormtaylor/slate/issues/4833, which is surprising as it doesn't look like some rare edge case, and breaks something that seems to be like basic functionality for an editor. Had to re-consider.

We do. We have one React app running on multiple instances that service different customers and not all customers need the same set of features. Some of features are only supposed to work on our staging instance until they're ready for production.

I'm sorry, I haven't read the article, maybe it's explained there, but as far as I understand by 100 hours they mean that the telescope was sitting there for 100 hours exposed open like a camera, right? How come the image is so sharp then? Wouldn't all those galaxies be constantly moving and end up blurred in a photo?

So cool! If you're into that kind of stuff I strongly recommend trying out this little gem https://urbanlienert.com/miditouchbar/ It's a touchbar midi-keyboard, it displays two full octaves and also has some other controls like volume and panning for the current channel and some others. But I mostly use the keyboard only and it works great with Ableton Live. Much better than one octave on your computer keyboard when you want to play while laying on a couch with your laptop! I'm really happy I've found it and it makes the touchbar really useful for me.

Git is not complicated. Version control is. If you sit and think hard enough about what you'd want a VCS to do, you'll come up with about the same set of features, I believe. And then think about how you'd implement those in an abstract CLI tool. So, as I said, it's the process that's complicated and that complexity can't be hidden behind just one simple button (or one CLI command).

I couldn't wrap my head around git for a while when I started. Some time later I decided to write a procedure for our branching flow at work. I wanted it to cover all the common cases like: checking out a branch, squashing and rebasing, undoing things, amending commits, etc. All of which I knew was possible with Git, but I didn't feel comfortable with most of those operations and had to go to Google almost every time. So in order to put that all down in simple steps with some short explanatory comments I, obviously, was supposed to very clearly understand all of those cases myself to be ready to answer some questions and moreover to be sure that each step is a correct way to do git and it wouldn't cause any permanent damage to anybody's repo. To get that understanding I created a few nested directories with some really small text files in them and used those to actually run and inspect consequences of various git commands which took me, maybe, about two hours maximum. I've never had a single problem with git ever since.

Oh, did I? But as far as I remember, not having to figure out classes was one of the official reasons why hooks came to be, which was clearly stated in the corresponding blog post, I think.

Got about the same feeling, but then I noticed that this free personal plan allows only 5mb of file uploads as opposed to the unlimited uploads in the paid plan, which is one of my use cases – I store quite a lot of files there as a personal software archive, and then I felt relieved.