For developers, Apple’s Safari is crap and outdated

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • Wekan

    The Open Source kanban (built with Meteor). Keep variable/table/field names camelCase. For translations, only add Pull Request changes to wekan/i18n/en.i18n.json , other translations are done at https://app.transifex.com/wekan/wekan only.

    https://github.com/wekan/wekan/wiki/PWA#ios-safari

    And that app icon does open PWA app full screen.

    I'm maintainer of Wekan https://wekan.github.io , Wekan also works as PWA app.

    For best mobile experience, enable drag handles:

    https://github.com/wekan/wekan/issues/3755

    There has been fixes to HTML/CSS/JS so Wekan also works well on Safari.

    Apple M1 with Safari has fastest Javascript execution.

    Safari works well enough for me.

  • caniuse

    Raw browser/feature support data from caniuse.com

    You mention a simple site with HTML and CSS. That is actually quite funny in a discussion about Safari as CSS is one of the areas that Safari is behind other browsers. A site with those frameworks would very likely work better in Safari than one without them (but yes I dislike them too which is one of the reasons I dislike Safari).

    https://caniuse.com/

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  • standards-positions

    > My case was a WebBluetooth based download of data from a web page.

    Web Bluetooth is not a web standard. It’s a Google API that only Blink supports. Firefox doesn’t support it either and doesn’t plan to:

    > This API provides access to the Generic Attribute Profile (GATT) of Bluetooth, which is not the lowest level of access that the specifications allow, but its generic nature makes it impossible to clearly evaluate. Like WebUSB there is significant uncertainty regarding how well prepared devices are to receive requests from arbitrary sites. The generic nature of the API means that this risk is difficult to manage. The Web Bluetooth CG has opted to only rely on user consent, which we believe is not sufficient protection. This proposal also uses a blocklist, which will require constant and active maintenance so that vulnerable devices aren't exploited. This model is unsustainable and presents a significant risk to users and their devices.

    https://mozilla.github.io/standards-positions/#web-bluetooth

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts