travellingprog

yeah, you're right!

TanStack Query (fka React Query) is a REST client similar to Apollo Client, with many of the same pros and cons: https://tanstack.com/query/latest/docs/framework/react/overv...

Another alternative that I have liked for replacing Make as a task runner is Task: https://taskfile.dev/

One major thing that has held back Web Components, IMO, is that the standard never provided a JSX equivalent: a convenient declarative, condensed way to express your component's structure along with event handlers. So if you choose to build web components, unless you want to have a terrible developer experience, you're still going to reach for a library anyways, like Lit (the successor to Polymer). Only unlike using popular libraries like React/Vue/Angular, the ecosystem, community and resources at your disposal will be much smaller.

Yes, Obsidian by itself reads and creates files in a folder of your choice. The folder is considered a "workspace" and you can create/switch to other workspaces if you want. There's desktop apps and mobile apps. Aside from Markdown files, you can store and display images, audio files and video files (haven't tried that last one though).

However, you can choose to backup and sync your workspace across multiple devices using a cloud service. The most pain-free way to do this is by buying a subscription to Obsidian Vault. This is also a good way to support the development team, since the main product is free. When you store your workspace on Obsidian Vault, you can choose to specify an encryption key, so that theoretically nobody at Obsidian should be able to read your data.

But there's nothing stopping you from using other cloud storage services. There's even a community plugin you can find to use a Git repo for storage.

They explicitly mention that they accounted for that in their calculation

My personal experience for the last couple of years is that the "checkout with Paypal" option on most sites is buggy now. After the Paypal portion of the payment flow, the redirect back to the original site fails. The redirected page will either show me an error message or I'll be somehow redirected to the website's root page.

I've stopped using the Paypal option even though I really want to use it, because it makes me uncomfortable providing my credit card information to so many sites. Not sure what's changed, it used to work quite well. My guess is either there's a bug on PayPal's side with my account, or the PayPal integration has gotten more complicated and many websites have not kept up with certain changes.

Never used it, but looks like Microsoft Project would fit that box.

This link doesn't work for me in Canada, because of some faulty re-routing that Kaspersky's backend is doing (keep getting redirected to https://www.kaspersky.ca/fr). This one does: https://usa.kaspersky.com/blog/hacking-agriculture-defcon29/...

there are existing startups that specialize in ID verification. E.g. in my current freelancing gig, my client uses Passbase.

How much longer till people can start receiving a Prime delivery of an ounce of fine Amazon Basics Indica?

What excites me most about Node upgrades are the introduction of new native Javascript capabilities, because of the underlying V8 upgrade. You can figure out what those capabilities are on this website: https://node.green/.

You have to scroll down all the way to "Node.js ES2021 Support" to start seeing features that work in Node 16 but not Node 14 (the current LTS version). Of course, it's possible to use Babel to bring those features into Node 14, but I enjoy leaving it out of my toolchain when possible.

You don't need to have 1:1 equivalence between API resources and database models, though. For example, you can create an API resource called TweetActivity, and then the backend code for GET /tweet-activity could put together a database query that grabs all the tweet likes, comments and basic commenter info (name, profile image), from different database tables, into a single new object. You can give that object the same ID as the tweet itself, and you can put a cache layer around that endpoint to, for example, save that response for the next 1 minute.

That being said, one thing you give up is providing a standard way for the client to specify which fields it needs returned. For example, a client might want to dig deeper into the commenter profile info. GraphQL's resolvers architecture opens up that possibility immediately.

It's not guaranteed to get software updates, but Pixel 2 is able to run Android 11, and so I believe it will continue to get security updates so long as Android 11 receives them. But it won't get access to Android 12 whenever that comes out and I agree overall that the support period for smartphone software is way too short nowadays.

I think the US site doesn't, but the Canadian one does. If you follow the link below, you'll see there's a Best Buy Only toggle. That being said, it's nice that the let you quickly hide third party items.

https://www.bestbuy.ca/en-ca/brand/Samsung

From my experience of trying to learn Rust (got almost halfway through the manual and then put it on hold), I would add that having all these ways of doing the same thing is also confusing from a beginner's perspective. As a noob, I have no idea what the timeline is of when feature A was introduced that does the same thing as feature B. Also, I kept having to dig around to see if feature A added any type of improvements (other than syntactic sugar) over feature B.

I've been a freelance full-stack developer for the past 1.5 years. I never bothered trying out Upwork, because I had the impression the price competition there was insane, so I can't comment on the experience there. But I've been on Toptal for the past year and it's been an overall great experience. Not only have I not had an issue being paid, but Toptal actually guarantees my invoice payments: basically there's a clause that states that I can expect a payment from Toptal within a few days after the invoice due date, regardless of whether or not the client actually paid the invoice.

The issue isn't just that some smart contracts are buggy. After all, all software should be expected to have bugs at some point. The bigger issues are that a)the source code can be very visible, making it easier to figure out how to exploit than traditional code running in an isolated server, and b)recovering from an attack can be incredibly difficult (such as needing to create a fork of the blockchain pre-attack).

I've been using Joe's Own Editor the past couple of years when I want to do basic view/editing in terminal (I use Sublime Text for development). Really like it because it provides syntax highlighting for a ton of file types, let's me get around with arrow keys/mouse, and gives me an easy way to look up keyboard commands I may have forgotten.

https://joe-editor.sourceforge.io

You can install it with your OS's package management system, and there's a Windows installer on the site.

I did adjust some of the default settings, which are configured and well documented in a .joerc file.

Take a look at redux-actions. I use it on all my React apps and it cuts a TON of boilerplate for me.

Regularly occurring major versions, with only a small amount of changes, has actually kind of become seen as best practice in the JavaScript community. React, Node, Angular and a ton of other popular tools now release a major version update every year or 6 months. The reasoning is that by taking small, backward-incompatible steps, then developers are more likely to make the effort to install the latest update.

To understand the problems the community is trying to avoid, one only needs to go back to 2015-2016, when Angular 2 was released. At the time, AngularJS (aka Angular 1) was extremely hot; it had in record time become THE framework for any front-end developer to learn, and it looked set to dominate the landscape for years. And then, Angular 2 came out and it had a TON of changes. The learning curve of some elements of Angular 2 was very high for the average developer (TypeScript, reactive programming). And worst of all, the "migration path" from AngularJS to Angular 2 essentially amounted to a rewrite of your front-end application. Most never bothered updating their app, and most devs moved away from Angular, especially when React was released. All of that AngularJS experience that we accumulated became "outdated" in the span of about a year.

The Windows Phone OS usually gets pretty good reviews. The lack of premium phone hardware parts until recently made MS create a very lightweight but pleasing OS. But it still suffers from a lack of app selection. And for me, I personally prefer the customizability of Android.

If you're a camera geek though, the new high-end Windows phone are very appealing...