Hacker Newsnew | past | comments | ask | show | jobs | submit | more code-is-code's commentslogin

No this is not a good thing. Binding workers right to political views is dangerous and other countries show that unions can work without any party propaganda.


This is so confusing, "workers rights" is political by definition.

Aligning to a party can be argued, I'd say it's best to break things up into policies more than "teams" but still.


Why is it bad for unions to support political parties, but fine for shareholders?


Fighting for "workers rights" is a political position.

Maybe you're making a distinction between party politics (e.g. endorsing specific candidates) and pushing for general policies, but I think it's incoherent to claim that labor unions are apolitical.


The point is that joining a union shouldn't necessitate supporting a certain political party.


It doesn't. You can join a non-affiliated union or even opt-out of political campaigning and contributions.

It's just not all that common.


That's good then.


This. Same happens with the sms verifcation in microsoft teams. On older devices switching to the sms app will restart the teams authentication process. So you have no chance in every typing the correct 2 factor sms key.


Have a data backup strategy before you save critical data.


They just want to protect you from yourself, do not take it personal.


I don't really, and I am polite and do thank them for the info they give / the concern they express. It just surprises me a little that they don't consider this normal.


Just dump it on reddit like everyone does. Especially projects that do not sell something are mostly welcomed.


I guess that’s a good enough answer hah. You’re basically rolling the dice, but if you’re honest maybe you won’t get thrown under the bus


Getting your post removed by a mod.... isn’t really that bad.


I got shadowbanned from the entire site for years for posting a thread in two subreddits about a small indie video game I worked on for six months full time and wanted to share (in r/games and r/indiegaming, I believe).

I didn't even realize until a moderator told me they had manually approving (some of) my comments for the past six months.

I didn't submit many links but I was an active commenter, and had about 1,000 comment karma at the time.

That really sucked.


Yeah this is the shit I am worried about. Your fate is basically in the hands of moderators, and the mood they happen to be in when reviewing your content...


Forbes is so broken on mobile


That's what I just discovered, too, using Android Chrome.

So, out of curiosity, I switched over to Android Firefox and turned on "reader view." Much better!

https://support.mozilla.org/en-US/kb/view-articles-reader-vi...


"Reader view" on Firefox is one of the best inventions ever ;)


If you love hasura and want something like firebase, please check out the tutorial with hasura + RxDB. It is like having a firebase with better offline-first and more features and of course without vendor lock-in.

https://hasura.io/blog/building-an-offline-first-web-app-wit...


What I liked with Firebase was how easy and fast everything was. One-click create a new project and everything was ready to use.

It's this developer experience I want to mimic with Nhost. By providing a managed backend with simple to use js-sdk (https://github.com/nhost/nhost-js-sdk).


I'm a web entrepreneur and for my project i've been using Parse server project (1) implementation by Back4app (2). For the non initiated, Parse server is a API server module for Node/Express + mongo + websocket and stuff you need to run a commercial app like auth, role management et all.

We chose this because :

1.Open source (no vendor locking although now i'm sure if i had to move from b4a it would be a small PITA 2. Ready to use 3. actively maintained (graphQL have been implemented although we have not used it yet) (3)

My question is : should i invest time on discovering nhost for my next POC ?

(1) : https://github.com/parse-community (2) : https://www.back4app.com/ (3) : https://docs.parseplatform.org/graphql/guide/


Yes! The main advantages for me with the Hasura/Nhost stack is:

1. SQL (Thanks PostgreSQL)

2. Instant realtime GraphQL (Thanks Hasura)

3. Zero vendor lock-in


> 3. Zero vendor lock-in

This is wrong. For basic features that are absolutely needed for a real-life app you will need the "Pro" hasura license.


No you don't.


I had the opposite experience with Firebase.

Amazing at first, but quickly fell apart when I had to implement any sort of meaningful business logic.


Yes I agree with you. With Hasura there are 3 main ways to handle business logic. We use the first one at Nhost and it's working (and scale) very well.

1. https://3factor.app/

2. Actions - https://hasura.io/docs/1.0/graphql/manual/actions/index.html

3. Remote Schema - https://hasura.nhost.io/console/remote-schemas/manage/schema...

I know Hasura is actively working on this exact issue and they just released Actions (second option) and I think we will start to see a standard/best practice approach to business logic soon.


Having tried remote schemas and reading about actions - I should say it doesn't feel right.

@elitan - just checking nhost. Features sounds promising.

Did you use hasura for building nhost's backend as well ?


Yes Nhost is built on the same stack you get with a new Nhost project.


If you like PouchDB, you should also check out RxDB. It is build on top of PouchDB and is optimised for realtime-applications where you can subscribe to queries and stuff.

https://github.com/pubkey/rxdb


Doing API-first.

Start with defining the swagger.json Then generate:

- frontend-typings

- frontend request services

- backend routes and DTOs

- database fields

- use angular-jsonform for forms

- use the swagger for frontend validation

- use the swagger for backend validation

- use the swagger to discuss api changes with the client

This saves half of developing time and prevents 90% of your bugs


How though? All of the swagger open-api tooling is REALLY bad or abandonware. Did you write your own?


I can't speak for the GP but the way I've dealt with that is by using the tiny subset of tooling that isn't really bad, and supplementing it with some custom patches to make it also work.


RxDB maker here.

You can do conflict-resolution by subscribing to the changeFeed and when multiple versions with the same revision-height exist, you create a new version with a 'merged' document. Depending on your dataset this can be tricky and painful.

RxDB can only be used with javascript and will likely ever be.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: