Ben here, one of the co-chairs for the WebView CG. Super chuffed to see this pop up on hackernews today!
For a little context, our group is currently focusing our efforts this year on improving WebView compatibility data. The project is still very young and we’ll keep chipping away at it but please feel free to reach out and engage! You can find the repository here:
https://github.com/WebView-CG/Compatibility-Data-Project/tre...
Looks super cool! Clearly an idea that people want - I built something similar to this almost two year ago [1] but your project is a lot more fleshed out. I like that you actually used websockets instead of my hacky approach of using an http stream.
I’m hoping to get back to everyone as soon as possible. I hope you can all appreciate that I’m a human being and this has been a lot!
In the mean time, I wanted to repost my last comment on the GitHub issue thread [1]:
Hey all, we plan to respond to your feedback but I want to be thorough which will take time and it’s the end of a Friday for me. We wanted to give a quick TL;DR:
- This is an early proposal that is subject to change based on feedback.
- The primary goal is to combat user tracking by giving websites a way to maintain anti-abuse protections for their sites without resorting to invasive fingerprinting.
- It’s also an explicit goal to ensure that user agents can browse the web without this proposal [2]
- The proposal doesn’t involve detecting or blocking extensions, so ad-blockers and accessibility tools are out of scope.
- This is not DRM - WEI does not lock down content
- I’m giving everyone a heads up that I’m limiting comments to contributors over the weekend so that I can try to take a breath away from GitHub. I will reopen them after the weekend
This is going to be the year I improve at climbing. I absolutely love the hobby and have done it on and off for years.
I’m at the age demographic where I see a lot of folk feeding into the hustle culture. While I think it’s important to keep the future in mind, I also want to recognise I’ve reached a pretty good point in my life and would like to do something that won’t improve my career in any way.
One important reason for coding questions I haven’t read in the comments is the need to avoid the interviewer’s personal bias. I’ve seen a lot of people say they can feel someone is a bad interviewer but how do you quantify that? Large corps need to protect themselves.
They also need to make candidates feel like they were tested using the same criteria as other candidates.
I had some time off last week so I built a little tool I've been planning on using for a while now.
Thought I'd just comment on my motivations for building this.
I bought a little chromebook tablet to take on holidays. I've been enjoying the experience of using a remote IDE to code on my personal server.
I thought it would be neat if I could quickly make myself GUIs for other utilities on my remote server that get rendered on my chromebook. Doing this like being able to run bash scripts remotely.
I start utility scripts with this tool and then just use ssh port forwarding to view it locally.
The fun bit is the application itself is then just written in python.
There are some similar alternatives[1] but I wanted to be able to write GUI elements like ImGUI so I decided to build my own tool in the end.
I just wrote it in python because that's what I've been using at work lately.
> I can hear people asking: “Isn’t it a bit early to predict that, given that we’ve only seen two products?” It’s a very fair question. But it definitely seems like a first step — to me, the Mac Studio line is a clear successor to Apple’s iMac Pro.
I was under the impression that apple is planning on releasing one more M1 device and that could be the iMac Pro [1]. This article feels quite hollow to me.
Interesting! So does safari have different storage rules depending on where the web app is accessed from? Are there docs detailing what else might operate differently? I wonder how many web devs test their apps under the different constraints.