I am from Europe and I have worked with many Europeans, Americans and Asians. Quality of sub-contractor colleagues from India was, same as from anywhere else, directly proportional to what the company paid for them. Good pay = skilled and hard-working. Cheap labour = barely any skills and hardly working.
Someone brought up the topic of JS and screenreaders upthread.
Screenreaders can work fine with JS. The pain points are:
1. Use of JS to reimplement standard HTML widgets. This has broken my screenreader more times than I care to remember.
2. All of this user-irrelevant garbage, like the dialogs, the social media buttons, and so forth.
I remember a few years back trying to pay my electric bill. Yes, I was
using a JS-capable browser. I couldn't actually pay my bill, but there
were plenty of "follow us on Facebook" and similar.
Like seriously, folks, I just wanna send you money.
Really, this should even be something I could do without JS.
Another example: we do online shopping at https://www.fredmeyer.com.
Their website is absolutely terrible, with all of the busyness, some of it user hostile.
Seriously folks, I just want to give you money for product, not follow
you on facebook.
Some sites get it really, really right. I play chess on lichess.org.
That site requires JavaScript. And I don't see any way that it could
possibly be avoided. But it works beautifully with my screenreader.
It's snappy too, even under Firefox on a Raspberry Pi.
I used to be a hard core "screw JS" guy. I've softened my stance, because
I know it can be used correctly and to great effect.
If no government bans it and mandates Linux kernel to be rewritten in Rust (and all higher language FFIs to be compatible with Rust rather than C), it's here to stay.
Edit: though I thought about it a little more. The more interesting question is regarding the standard library, rather than the compiler. Applying different licenses to the two is not unusual (gcc is GPL, glibc is LGPL). From what I can see, the standard library is embedded entirely into the compiler, and thus yeah, I do think programs that use this would actually have to be GPL. Not that that's a bad thing though :)
More important than the standard library (which isn‘t so standard, just conventional, see musl) is the GCC Runtime Library, which is GPLv3, but with the "GCC Runtime Library Exception".
There is also an interesting question about license compatibility between GPLv3 and GPLv3 with RLE, but that is mostly ignored by everybody.
Unless KamilaLisp specifies exceptions to the GPL, it means that if you ship your own KamilaLisp program in a way that is combined with KamilaLisp (for instance compiled into one big executable that includes the KamilaLisp run-time) then the entire combination has to be distributed under the GPL, meaning that your program has have a GPL-compatible open source license.
Programs that are not combined with KamilaLisp, only requiring an installation of KamilaLisp for their execution, almost certainly don't have to be GPLed.
Beg to differ. Maybe you can decipher all this license stuff but I can't and I'm sure OP was asking people who are more savvy about it to get an answer, not to be lectured.
I don't understand the legal speak on these pages. What does your comment mean? That I'm supposed to reach a certain level of understanding of open source terms to be allowed on here? Sounds extremely narrow minded
I told you I have read the terms of these things and don't understand them. You have like 5 comments on here and you're lecturing people on the culture of HN. This is why your comment was flagged. Get over yourself
And what's the point of having Lisp if you can't use it? Unpopular opinion alert: Bigger companies want programmers to be replacible resources which means they need to have huge talent pools. If you choose your tech stack for the fact that you can retain your people for only 12 to 18 months, you can't effectively use any of the advantages Lips languages offer to you.
I remember jQuery from it's heyday when we used it as a replacement for Mootools. Since many people are going from React to HTMX, maybe we've made a full circle and we'll see web using just plain jQuery as well?
I came up in a similar era, I don’t think back fondly on those messes. Doing a modern app with accessibility, mobile support, real time updates, visualizations, and maybe a few PWA features with just jQuery sounds incredibly unpleasant.
I’m waiting for the HTMX hype train to meet reality too. Programming your app in pseudo attributes with a DSL is going to wear thin quickly.
I think that many websites even nowadays don't need all that jazz and many would improve if less JavaScript was on them. How many times have you loaded a website only to watch a couple of JavaScript "spinners" for everything to load only to click somewhere and everything started again? MS Azure management is one of such sites.
SPA with real time updates, complex layouts to be mobile-friendly, real-time updates of many components, endless scrolling and PWA features would be a total PITA. Yes, I don't disagree.
The vast majority of web apps I have seen so far don't need to be like that.
I live in the US in a "platinum rated" bike city (so there are a relatively high amount of bike commuters) and have gone through drive throughs on my bike a handful of times. Every time I have been served but told not to do it again.
Pedestrians are not served at drive-through windows at least in part because they are more dangerous to the workers. A driver at a drive-through window can't open their door, the window is very close to the drive-through kiosk but the kiosk is usually much higher (in a sedan) making it hard to climb out through the car window...they've also got a license plate.
During the pandemic most fast food places locked their lobbies and only did drive-through, which meant truckers couldn't get food because workers wouldn't serve them due to policies the companies refused to adjust.
I remember some police departments were volunteering to go through the drive-throughs for truckers.
The nightmare is being shot through a drive-through window and not even being able get a license plate. I've never had a car driver's license (only motorcycle) and I completely get it.
They're not staffed the same way at night as they are during the day.
As much as the political salesmen love to emphasize the differences, Soviet style bona fide government central planning and American style corporate central planning have many commonalities.
I've had some luck asking a stranger in a car to trip the sensor and then back up so I can order and walk though. Once your order is in its more work to say "no" than it is to say "yes but don't do it again"
Some cities like Portland, Oregon have made it a violation of city code to refuse to serve pedestrians and bicyclists through the Drive Through window if the lobby is closed.
There are still some businesses that violate this, but at least you can report it and they will be fined, and threatened with revocation of their business license.
Good. Let's make this federal law. These restrictions are ridiculous and we stand no chance of eliminating car culture without eliminating them. I wish I was kidding, and I wish it were just a trollish joke to say "you should be able to bike through Taco Bell at 2am", but if we're gonna eliminate car culture in the US, we can't just do it in the downtown cores of Chicago, NYC, Seattle, SF, etc. We gotta do it everywhere, and a lot of "everywhere" in the US is drive-thru this and drive-thru that, especially once you get out into the boonies (which of course need more infrastructure work to become bike friendly in their current states, but also, rural bike trails can and should exist, but there'll be little reason to use them if you can't stop anywhere along the way to take a break - and the rabbit hole continues from here)
After 9 or 10 PM that's exactly how it is here in TN, USA. Dine in is closed and the drive through won't take you on foot or on a bike. I think most franchises have a blanket policy against serving people without a car to intentionally exclude... Certain People.
But why? They would have to allow these same “Certain People” in their lobby from 7am until 9pm when their most affluent patrons are probably coming in for lunch, after soccer practice, etc. At the drive through there is barely any interaction between staff and customer much less between customers.
I would assume the homeless, certain income ranges, etc. That's the real reason to close the lobby but keep the drive through right, so people aren't hanging around in it and resting at night?