With an open source and potentially local-only device, you can have your voice assistant and keep your privacy.
390 karma · joined August 15, 2019
With an open source and potentially local-only device, you can have your voice assistant and keep your privacy.
Maybe “syncing ebooks with audiobooks” would be clearer? Also entirely possible this is just a me problem, not a general one.
Really cool project!
Something as simple as calling a .NET function that doesn't have F# bindings forces a change (e.g. `someLibraryFunc(arg1, arg2)` instead of `f arg1 arg2`).
This gets worse as libraries force you to instantiate objects just to call methods which could have been static, or use ref parameters, etc.
I say this as somebody who loves F# - you do absolutely have to know .NET style (which really means C# style) in addition to F# style. It's extremely pragmatic if you're already familiar with C#, but I'm not sure how wonderful it is if you come in cold.
> no it didn't
If this is how you think the conversation went, I suggest you reread both your own initial comment as well as my reply.
My personal anecdote is that I have yet to have any Philips LED bulbs die on me. The oldest ones I have are from 2012.
In general, print-based debugging requires a greater degree of specificity. If you know exactly what you're looking for it's great.
If you are performing a more exploratory sort of debugging, a decent graphical debugger will save you a ton of time.
We have multiple sitting Congressmen and other government officials still refusing to admit Trump lost in 2020.
It sounds like it's more for authoring cards on the tablet than it is for reviewing.
Nonetheless I now understand the point you’re making about the framing of “cheating.” Thanks for explaining!
More of those attending university are pursuing SWE-related degrees than ever.
Yep, tuple or "product type."
Yep, in F# type annotations can be either in prefix style `List<T>` or postfix style `T list`.
Also it's not like they've implemented a custom storage back-end, it's ClickHouse. ClickHouse itself thinks SQL is fine for querying time-series data (as do Snowflake and TimeScale, for that matter).
Ultimately of course Oxide can do what it wants, but the justifications provided in this doc are thin enough to make NIH seem like a very plausible explanation. Perhaps the problem domain is more complicated than just retrieving some time-series data out of ClickHouse, and the doc fails to make that clear.
1.2 doesn't go into nearly enough detail to be convincing, in my opinion.
GUI might be special a case because there are so many flavors of it, and half of them are abandoned dead-ends.