I see we can filter by topic tags (https://tildes.net/settings/filters), and that's nice.

What I'd also like to be able to do is filter out by site:somedomain.com.

I went to look at the tildes source code, but, in my brief visit, it didn't strike me as something I could quickly cobble a pull request together for.

The main thing I want this for is to filter out YouTube. Nothing wrong with other people liking Tildes recommendation of YT videos, but I come to Tildes for things to read, not things to watch.

Hey all. I’m sure there’s a lot of new users making their way to Tildes this week. Let’s share some Letterboxd profiles to get the community going. I guess I’ll be first! Follow me if you have similar taste and I’ll do the same: https://letterboxd.com/plo/

I know quite a controversial and opinionated question, one that might easily get blasted with downvotes on a site like StackOverflow or even Reddit! Nevertheless, one which I believe is still relevant to ask and useful one even in 2023.

The problem with backend web technologies is that we are overwhelmed with choices. Whilst getting spoilt with choices seems like a useful thing sometimes, it might easily be an impediment in decision making too. Based on my experience, there are a bunch of useful stacks and I will work on any of them if you pay me to work as a freelance coder. Each has its own pros and cons but I'm yet to find the ideal one which according to me is something that should be easy to code and deploy while also better performing at the same time.

• ASP.NET: C# is the language I started coding web apps with in my last company and ASP.NET web forms was quite the rage back then. PHP was also gaining traction in the open source world and the webdev was mostly divided between the Enterprisey .NET aristocrats of Microsoft world and the poor PHP peasants of the FOSS world! One good thing about ASP.NET was performance. Since MS controlled the whole stack, they also put great efforts at making it work faster. The bad thing, of course, was dependence on a closed tech stack and a closed black box that generated JS functionality on its own.
• PHP: When I resigned from that company and started freelancing, I came to know about open source, linux, XAMPP, etc. That was when I realized that my own attitudes and thinking was more attuned to the FOSS peasant mindset than the wealthy aristocrat's! I didn't earn quite as much in freelancing with WP, Drupal, SuiteCRM, CodeIgniter, etc. but I found great happiness and contentment in being part of the open source process. Till date, PHP remains my favorite language for backend development and most of my web projects involve CodeIgniter or even pure PHP.
• Python: Flask is what got me interested in Python web development. The sheer minimalism and flexibility of that framework is what I found quite remarkable and quite a rarity in the frameworks world. And jinja2 template system was just fantastic. The other framework called django is more popular I think and I've worked on that too but Flask still remains my favorite. Flask is good in performance dept. too but I think it gets tricky once you start scaling with too many users.
• Java: I've never really bothered with Java web development except a few tutorial experiments on the Apache TomEE server. The multi-layered approach that Java takes not only has very steep learning curve but unless you're a very gifted programmer, it's practically impossible to beat the performance of interpreted PHP/Flask!
• NodeJS: Again, not much work here except brief hobby projects like http-live-simulator. The npm packaging system really turned me off initially with so many packages and issues with that system in the earlier days. Nowadays, I've heard that it's much usable but I've never gotten into it.

And now, we also have the evolving languages like Golang, Rust, etc. taking their baby steps towards web development too! Are any of them worth giving a try? If someone were to ask you for a backend tech stack recommendation while giving equal weightage to performance, developer productivity and ease of deployment, which one will you suggest?

Most of the world seems to be settled around Chrome and Safari these days. I remember using Firefox a long time ago myself but then everyone started switching to Chrome and that also turned out to be a natural path of least resistance for web developers like me who had to test web apps in local environment.

This switch happened in circa 2015-16 if I recall correctly, many other browsers have evolved since then and people are looking at alternatives. The Android Kiwi browser, for example, is a great alternative for power users on mobile who need plugins but Chrome won't allow that. Other alternatives have evolved too like Brendan Eich's Brave browser which seems to be promising. Anyone here tried that yet?

I have half a mind to go back to Firefox but I recently learned about how Mozilla Corp is also funded by Google and that turned me off. Wouldn't you rather want to deal with the Devil directly instead of the Devil's assistant or sidekick!

And then there are also those who use Garibaldi, Midori, etc. but I can't go that purist way. I'm way too dependent on the digital way of life and sites like amazon and flipkart won't work in those browsers. What do you think should be the right path ahead from here?

Ever since I moved to a place with an airport nearby, I've been wondering about those flight deal sites -- the ones like Scott's Cheap Flights, Mighty Travels, Thrifty Traveler, Faredrop, Secret Flying, Dollar Flight Club, etc (those are just the ones I found off a Reddit thread on r/TravelHacks).
Has anyone here had any experience with these paid services?

Also, does anyone know of a way I can search for a start and end point, and find other airports nearby to fly out of for much cheaper? I remember having used such a site earlier but cannot for the life of me remember its name now :-(

I figured that more than complaining about the dearth of random and weird websites, I might ought to contribute something. I almost went to MassArt for new media installations. In those days I was a web monkey with a solid design bent and very orthogonal thinking. I still have a smidgeon of the thinking, we'll see what I have left of my design skills, but my tech skills are hopeless. Back then my tools were freehand, dreamweaver, bbedit, photoshop, flash, Perl, Solaris, mySQL. My last website was done with rudimentary css.

I would like to get right to the design and expression phase, I don't have an inclination to dive into coding. I also don't want to worry about security. I'll throw a few bucks down.

I'm still comfortable in photoshop, but would like a more fun tool. I cannot stand illustrator, and would love to have a vigorous chat with the folks at Adobe who chose to promote it and shelve freehand. Better yet, an even more vigorous chat with the moron at the FTC who approved Adobe's buyout of macromedia. You can bet that will be on the website. Is there any equivalent to freehand? I saw the post about a free, online illustration tool that came through recently, that might be a smidge rudimentary. What about dreamweaver? And how to publish? I don't care to learn about content management, scripting, databases, etc. if I can avoid it.

Bonus if there are AI tools to help.

Yesterday, Adsense support sent an email to their users regarding their upcoming policy changes. This primarily affects how subdomains are monetized. Going forward, your subdomains inside the primary domains in the "Sites" section (www, etc.) won't be allowed, any existing ones will be removed and their rules will be merged with the primary domain (such as example.com).

Furthermore, what constitutes a "Site" will also change henceforth. You can only add a primary domain (such as example.com) and the subdomains which are listed on the public suffix list (such as github.io, blogspot.com, etc.). Thus, your own subdomains (such as xyz.example.com or www.example.com) won't be allowed in Adsense.

I don't know what they will achieve by doing this considering they already vet and audit each site before approving them for adsense? In any case, other alternatives to Adsense exist such as Propeller Ads, CJ Affiliate, etc. for those affected by this move but I don't know their efficacy.

Title says it all. Bootstrap+jquery has been my default route and path of least resistance when it comes to web development. Perhaps because I'm coding since a long time and belong to the old school when modern libraries like react weren't yet invented yet?

I had tried to meddle with Angular.js 1.0 back in those days but was soon disillusioned! It was cool and cutting edge but highly opinionated. It tried to do so many things under the hood that I soon quit the effort and the word "Angular" was stigmatized in my mind ever since! I don't know how different today's typescript based Angular is but that stigma or phobia prevents me from even looking at that direction!

React is another cool technology which everyone is talking about and I'm sure it has some merits. But I'm not sure exactly what React brings to my development workflow which jquery doesn't already do. Can you tell me some specific advantages or pros of react over jquery which can motivate me to learn the former and let go of the latter? What should I do?

I'm working on an app idea, it's going to be "API first" in design which means there is a clear separation between the backend and frontend. Former will be accessible through a REST API and the latter can be simple HTML without me having to delve too much on it. The idea is that the end users or clients will write their own front-end interacting with this REST API in future.

Firstly, I want to know where to start. Writing a REST API seems quite easy and simple for me as a backend engineer but I've never implemented a "pure API" app in practice. Do you just validate the headers, do the crunching and return back a JSON response? What all must you take care of here?

Finally, authentication and session handling is something very important here, isn't it? If I make use of session feature in the REST API (like PHP sessions or Django sessions, for eg), authentication will be pretty easier. I don't have to worry about encryption as SSL/TLS would be already doing that for me through the browser. But then what is the downside of this method? Why do so many people use JWT tokens then?

Coming to JWT tokens, is that the only way of encrypting/validating REST APIs, or are there others? My biggest concern here is scaling and performance. I'm willing to implement the most efficient path here, the one that gives the most performance using least resources.