The only thing I ever want out of these chart libraries is to be able to theme them. Does anyone know how customizable the theming for ECharts is?
I was curious about this too, and I found https://echarts.apache.org/en/theme-builder.html
Readit Newsharunurhan commented on Apache ECharts echarts.apache.org/en/ind... · Posted by u/tomtomistaken
harunurhan commented on Code is run more than read olano.dev/2023-11-30-code... · Posted by u/signa11
Some users are not using a system because they like it but because their company bought it.
In those situations biz > user by definition and the developers end up having to cater to the needs of the middle managment of their customers rather than the needs of the actual users. The price of not doing this is failing to win the contract. Users then get locked in to whatever crap you have time to provide for them while you're really busy implementing new features that middle managment like.
You essentially only need a nice looking login screen and some sort of reporting and the rest.....doesn't matter much.
I am being a bit cynical but it does pay as an engineer to know if that's fundamentally the kind of company you're in.
An online retailer, for example, is hypersensitive to its users and I know of at least one that has different versions of its website for different countries because they know that Germans like X and Americans like Y - small changes make a huge difference to sales.
Other companies have no sensitivity to the usability of their products because the people who buy their products are never the users.
I guess "online retailer" example could be extended to many of the companies that are creating consumer products.
Agreed, it really works too well for how simple it is!
We implemented it in ES6 as part of a uni project if anyone's interested: https://github.com/gurgunday/onedollar-unistroke-es6
it works really well if all you are drawing is an eclipse ¯\_(ツ)_/¯. Could be a bug in the client or your implementation of $1.
Ok now I’m curious what beer is served at CERN. I am not familiar with any Swiss beer and only a handful of unspectacular French beers.
I don't think it was particularly good or bad, when I was there. I don't drink beer none of my friends ever said "this beer is great" or "this beer sucks".
Curious how you handle `request.formData()` in Form Actions and ensuring type safety there.
Like any user input, you do runtime type-checking and validation. TypeScript is especially great for that because it has type narrowing [0].
[0] - https://www.typescriptlang.org/docs/handbook/2/narrowing.htm...
harunurhan commented on AWS doesn't make sense for scientific computing noahlebovic.com/aws-doesn... · Posted by u/lebovic
I see both sides of the argument, there is a reason why CERN is not processing their data using EC2 and lambdas.
The cost isn't the only reason
- CERN started planning its computing grid before AWS was launched.
- It's pretty complicated (politics, mission, vision) for CERN to use external proprietary software/hardware for its main functions (they have even started to MS Office like products.)
- [cost] CERN is quite different than a small team researchers doing few years research. the scale is enormous and very long lived, like for decades continue
- and more...
HPC and scientific computing aside, I would have loved to be able to use AWS when I worked there, internal infra for running web apps and services wasn't nearly good & reliable, neither had a wide catalog of services offered.
harunurhan commented on AWS open sourced the AWS console design system github.com/cloudscape-des... · Posted by u/wizwit999
I am really surprised how fast/responsive it is. Most UI frameworks feel clunky/slow and react ones feel even slower sometimes.
I think the trick is cutting down animations
harunurhan commented on AWS open sourced the AWS console design system github.com/cloudscape-des... · Posted by u/wizwit999
Delighted to see the developers at AWS incorporating react w/ TypeScript.
I hope this project stays active and the framework keeps a low overhead: I've spent some time ripping out chakra-ui from my sites due to its complexity making it hard to diagnose styling bugs between styled-system, emotion, etc. Mix that with a monorepo of UX components where packages depend on each other, and them being prebuilt. I could never find out why certain style rules wouldn't apply.
It looks like this project has an interesting thing: style-dictionary (https://github.com/cloudscape-design/components/tree/7433543...)
I'd be interested in reading a dev blog post on the architectural decisions (and lessons learned). Is there any decisions from other major UI frameworks that were trying to be avoided?
One more thing I've never seen before in a framework's documentation: Patterns (very practical and case-specific examples), https://cloudscape.design/patterns/patterns/overview/
Good job to the AWS team on this, will be studying it!
> One more thing I've never seen before in a framework's documentation: Patterns
I really appreciate this! btw some DS have that too
https://ant.design/docs/spec/overview
https://carbondesignsystem.com/patterns/notification-pattern...
harunurhan commented on We don’t use a staging environment squeaky.ai/blog/developme... · Posted by u/Chris86
flag = true
More seriously, at my old company they just never got removed. So it wasn’t really about control. You just forgot about the ones that didn’t matter after awhile.
If that sounds horrible, that’s probably the correct reaction. But it’s also common.
Namespacing helps too. It’s easier to forget a bunch of flags when they all start with foofeature-.
> the ones that didn’t matter after awhile.
Ideally you have metrics for all flags and their values, so you can easily tell if one becomes redundant and safe to remove entirely after a while.
I've also seen making it a requirement to remove a flag after N days, the feature is completely rolled out.
harunurhan commented on Zendesk pretends to be open source? zendesk.co.uk/help-desk-s... · Posted by u/tailspin2019
I bumped into this just yesterday, it's sad that the page ranks very high for "open source ticketing" :(