Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

Because in order to avoid paying taxes, a lot of companies balance books so that no profit emerges.


Yes, by paying for things and people. Because that's more valuable than paying taxes.

However, that only works if one's willing to forego paying shareholders dividends (which are paid out of net). Lots of people are not willing to do that.


Yes, but I tried to say "ok google" to my phone, and if I don't press anything, it doesn't switch on.

Not to say it couldn't, but by default, it's not supposed to be listening.

While alexi is.

My intent is different.


"Private by design so you’re in control."

Oh, come on.


That feature definitely is a privacy improvement though.


Was that paragraph meant to be clickable or extendable?

Because I wanted to read what they meant by

"With new easy-to-use, powerful privacy features, you’ll have peace of mind"

but noscript blocked any link or something.

"If you see anything that you’re not comfortable with, you can manage permissions right from the dashboard."

I doubt I can remove all permissions from Google (?)


> Was that paragraph meant to be clickable or extendable?

The next four sections expand on it: see what apps are using the mic and camera, option to give apps only approximate location data, app permissions dashboard, and the local computation for some data.


setting up is still unsolved, but:

- for librairy packaging and general dep maangement, poetry is the solution

- for packaging a web project and ship it on the server, shiv is the solution

- for distribution, half the solution is nuitka for compiling the program. Creating the installer is now the hard part


I haven't looked at Nuitka in a long time. Last time I did Windows support was not great and compilation took forever. I'll try it again.


Do you use Cue for generating config, or for more for validating it.

I kinda like Jsonnet, but it only generates.


True, though one may turn that around to say Cue's scope is too large while Jsonnet's is more "pure" while still enabling the larger scope.

Schema that describes data is itself just data and Jsonnet can describe both. While the various Jsonnet compilers do not "know" about any specific meta-schema in which to express schema nor of course any way to apply that schema to data for validation, one can create such systems with Jsonnet as the language and its compilers as a component.


True, CUE has quite the inspirational scope right in the name. It is actually what draws me to the language. I also like the theoretical foundations in being turing-incomplete. Functions and computation make configuration harder to understand and reason about.


I mostly generate yaml and json now that I've been using CUE. The cool thing about CUE is that it's really doing both at the same time. Types and values are just points along a spectrum of specificity, going from types to constraints to concrete values.

I found CUE because I needed something better than Yaml for generating code, or declarative application code. (https://github.com/hofstadter-io/hof). It was similar to when I found Go and replaced a bunch of C++. I gained way more functionality in my application while shedding more than 50% of my LOC.


Can you give more info on how "parse, don't validate" has been helping you? I'm trying to get on the train, but I have so much validating code.


Not OP, but "parse, don't validate"[0] says that data (including config, etc.) should go through a "parsing step" (no "shotgun parsing"[1]) which outputs specific data-types for the main processing code to deal with ("invalid states should be unrepresentable"[2]).

For example, we might have a "parsing step" which takes in Bytes (e.g. '[{"email": "[email protected]"}]') and outputs a 'NonEmptyList[ContactDetails]' (e.g. 'NonEmptyList(Email(NonEmptyString('c', "hris"), NonEmptyString('e', "xample.com")), Nil)').

Compare this to a "validate" approach, e.g. parsing the bytes to a 'JsonArray', and using a boolean function to check whether it's empty, and whether its entries match the 'contact details' schema. That's problematic, since (a) it leads to "boolean blindness"[3] (the function tells us 'attempting to get those fields should work', whereas the parsing approach actually gives us those fields) and (b) such a boolean function is actually redundant, since deleting all of its call sites (or forgetting to write them to begin with) would give us a program that still compiles and runs (whereas the parsing approach would give a type error: 'Given JsonArray, expected NonEmptyList[ContactDetails]').

CUE's approach seems to be similar to passing JSON values around, and occasionally performing validation checks (if we remeber to); i.e. validating, not parsing.

[0] https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-va...

[1] http://langsec.org/brucon/ShotgunParsersBruCON.pdf

[2] https://fsharpforfunandprofit.com/posts/designing-with-types...

[3] https://existentialtype.wordpress.com/2011/03/15/boolean-bli...


Its not clear how this complaint applies to a configuration language, since there is no mutability or change, configuration is statically evaluated.

I'd consider cue to be a config language that by and large tries to make invalid states unrepresentable.


As a python dev, nim was much easier to get into than Go, Rust, or even Zig.

If you squint, it looks like a toddler Python with strong typing, compilation and a few different API, espacially for managing finalisation.


I may be splitting hairs here but Python is actually a strongly typed language. It would be better to say nim has static typing: https://wiki.python.org/moin/Why%20is%20Python%20a%20dynamic...


The internet in one comment, ladies and gentlemen.


And just like that, the outrage about the photo scanning malware Apple installed on their iPhone is forgotten.

"The screeching voices of the minority" indeed.


First of all, they never "installed" anything, it was a future feature. Second, they delayed it (possibly indefinitely) after the huge pushback.


I heard they reconsidered.


Well, if you want events, you have lighter alternative. Redis pub/sub, crossbar... Even rabbitMQ is lighter.

If you need queuing, you have libs like celery.

You don't need to go full kafka


I do not disagree. Kafka is kind of a monster to fully configure correctly. Once they get rid of zookeeper it may be nicer to spin up and 'set it and forget it' sort of thing like the others.


Redis - it's probably in your stack already and fills all the use-cases.


Agreed. Redis pub/sub is underrated.


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

Search: