There's no reason to trust Apple. Numerous reasons to be on guard about any assumption relating to this company. From fading and variable service, quality of deliverables, security oversights, repair relationships and one sided contracts, use of vendors and stewardship of user data in China, ethical and legal positions with respect to taxation, privacy and due process there is absolutely no reason to trust Apple or their products. From the use of my phone and laptop taking weeks to repair and being unavailable to compromising messaging and data on the device or in the cloud. Apple and its products create a centralized area of exposure where their incentives and position are increasingly one-sided. Federal oversight is lacking and appropriate competition is as well.
that's arguable, the encapsulation web components affords is built into the system and simply being exposed by way of this bucket of technologies
When compared with React and similar solutions doing the same and similar thing(s) it runs circles around them... or am I misunderstanding the comment and is the position asserted that container queries (not web components) are the effect?
What is the inner-platform effect comment applied to specifically?
Why server side rendering? Content that needs rendering just put in the tree and target a slot. My perception was this is the best practice. I haven't used the lit included intl translation and am curious if and how these concerns work.
Great to see Deno going from good to better and better steadily over the past year. It is such a pleasure when compared with Nodejs projects. Always appreciate products that make life easier.
Personally I see infrastructure as the thing that gets qualified people to productivity and keeps them productive (jobs or whatever form that takes), and I also expand the notion of infrastructure to include a society and community with effective education and healthcare to maximize the human capital of the group. Given this I see infrastructure and the various components of it as decades behind in the US and Apple would be smart to take the direction. Just consider the process of applying for an SBIR or finding a job or starting a startup or getting from SF to San Jose, etc.
Apple and much US associated supply chains have already been moving away from China. Media is regularly coming up where the side effects are reported, for example the Foxconn contractor in India. The US lacks the infrastructure to leverage talent or capacity domestically. The only thing that will fix this is government policy--otherwise Silicon Valley would have decent transit, no homelessness and California would have its own State or region-level healthcare delivery network. The same things Taiwan has with only 23 million people that benefits TSMC (and the people there).
I'm very curious to see what happens to Intel. When the TSMC Arizona plant comes online in 2024 or sooner there doesn't seem to be much left for it to do that AMD and others are already doing more effectively. Perhaps that's too much an oversimplification, however it seems to be the sum of the various parts given as others have said here and elsewhere (and was my experience too), the performance of Intel hasn't changed much in about 10 years.
Deno is the likely final, last stop and resting place for most anything web related to this type of tooling. It includes about anything that is the kitchen sink and swiss army knife of the space. For anyone who wants to simplify their life, this is about it. I even bought one of the Deno stuffed animals from IKEA. https://deno.land/
I do not currently see it as worse and in fact I see it as better. If Google becomes the boundary behind which my information is shielded they are also the target for accountability. They generally seem a preferred option for this role relative to the others in the market (the little I know much about it). Further this seems a general good fit for their capabilities, business goals and role in society broadly, which is a position counter to the assertions the EFF appears to make. My position and argument is that Google should do what they are naturally doing and be held accountable for sensible privacy, etc by the law and watch that evolve. This seems both fair leverage of their market position and sensible use of it. Competition is freely able to develop their own niche, as is Brave and anyone else able to do. (For example why Mozilla hasn't developed VPN services, etc sooner is beyond me.) Hope this is constructive.
If it costs less than or equal to $10USD and works I'm all good with it. Please also include the common flu-types, HepC, HIV, etc at the same price point as well. We can move on to other things and ideally all be a little more productive with these strategies becoming more in line with going through a McDonalds drive-through.
Agree and have a similar experience so I use Jitsi https://jitsi.org/ instead and recommend it. If clients insist I simply ask they enable joining from a web client, otherwise unable to join. Jitsi works well and find it odd how remarkable mindsets become locked into options regardless of the accessibility and benefit of alternatives (great material for comedy, psychosocial study, etc). From React to iOS default apps to Zoom, it's an odd disadvantage of our human condition.
LitElement + native Web APIs, Deno on Google Cloud Run. Not novel as they've been rolling along a few years, but not as widely used/known. Easier to developer with overall: easier to manage state, loosely couple/compose components, better performance both in development and for end-use, easier to directly use native web APIs--both on the frontend and in middleware, potentially eliminating part or all of build processes.
Consider reporting this to your State and Federal trade commission and privacy enforcement entities. Moving forward it's likely useful to document the activity (screenshots and related, whatever is convenient) then followup to share the documentation with these groups.
Not many care about monopolies. We care and want fair competition. Each of the companies mentioned in your comment don't matter except where they are anticompetitive (FB is based on what Mark says alone and Amazon appears to be based on their Amazon basics and similar patterns, as I recall Apple has right to repair related issues tangent to this and Google and Apple colluded on fixing salaries, not sure about the details here...). None of this has to do with monopolies.
Excellent article and remarkably easy to identify the anticompetitive behavior which is the fundamental issue. Add to this CA Prop 22, among other related problems it'll be interesting to see what government does to exercise its power appropriately and encourage competition in the market. Appreciate the clarity Tim Wu and Wired contribute.
The things this situation posed in the article illuminate are that proper government oversight and distribution of concerns are a necessary part of balancing power. The tensions designed into a system help address its edge cases to varying degrees. And the article points out how to manage one of these situations generally--it's an excellent list of insights. Automation should be balanced with humans in the loop, automated systems are imperfect, humans are too. Balanced systems with separations of concerns yield good results. Discretion can be exercised and applied appropriately and the relationships with their respective concerns can sort out these edge cases and share that info when and where it furthers common interest.
Interesting characterizing engineering as honestly, horrifying, low-hanging and regarding one approach to typing as translatable to all practices and the underlying assumption it conveys a guarantee of reliability. I don't find any of those things to be true (in isolation or together). Of course I only know so much so there's that.
Most of those existing systems are like a Catholic wedding. The investment of time with those implementations is overly complex and unwinding it from your product becomes that much more complex and costly. Delegate those decisions to the professionals who are hired for the related expertise and point them toward the higher level goals--then hold them to that. They'll optimize their own workflow.
I'm not sure long timelines are a requirement. Finding product-market fit seems the aim and having components that facilitate quickly iterating makes sense--especially if the designers and developers can independently iterate in parallel (which is incidentally easily achieved with the right experience and management--and frankly the prior expertise is the time specific benefit). Startups as much or more than any group fail so I don't think anyone has found a formula otherwise the failure rate wouldn't be as high. If the staff can take the design system and leverage it for the next job that doesn't seem as poorly considered as many startup's direction. They did after all get hired to design something so if that system takes less and less time and becomes increasingly effective it might become their own automated side thing.
https://developer.mozilla.org/docs/Web/SVG/Element/use#brows... shows nearly complete green across the board, frontend tech years are like dog-years; without more info I'd suggest leaping forward to <use> <svg>; in other words it's not like the 1990s anymore--every modern browser have continuous updates, robust native APIs that make the majority of contemporary legacy tech workflows prior to 2017-ish obsolete, and Google's bot processes JavaScript as a mobile client by-default as I recall. Browsers are more consistent and robust in their implementations than ever before, making contemporary solutions easier to implement and performant both for consumers and developers--providing they know of these and use them.