In its simplest form, it's just a dump of the code intelligence information from a static copy of the code. This can power an LSP, however, without additional logic wouldn't be able to handle a project under edit, since the locations won't match between the indexed state and the edited project state; So it lends itself well for something like Sourcegraph that already displays a static copy of the codebase.
Uber uses SCIP as part of the LSP implementation for our Java monorepo (Pieces of which we've [open-sourced](https://github.com/uber/scip-lsp)).
Standardizing on SCIP has helped us generalize tools to be independent of the compiler/language ecosystem (eg we could do call-stack-analysis on any project that exports valid SCIP; do feature flag cleanup; find refs/impls across a wider scope than most LSP servers can handle due to memory constraints).
I've played with some 6Ghz 2$ microwave radar sensor and Software Defined Radios though I have not yet used 60Ghz.
Electromagnetic Waves are kind of magic when used in not conventional ways. I remember seeing the 2015 disney EM-sense video https://www.youtube.com/watch?v=fpKDNle6ia4 which is a non-radar way to listen to the environment.
I mean, in theory you setup 3 WiFi base stations and you can use WiFi in roughly the same way. No where near as accurate, of course, but you can easily figure out which areas of the house a person is in.
I don't see why this wouldn't be an even better way to do the same thing.
I definitely like this system of applying policies. Would like to see more than http though, like being able to set policies on execution time (e.g.: avoiding a RegEx DoS), filesystem access (e.g.: logger middleware can only write to /var/log/app), module access (e.g.: code that handles sensitive info like passwords can only load trusted modules), etc
Is this the future goal for the project or is it more of a PoC?
Timezones make scheduling team meetings hard, and if your organization ever becomes big enough to warrant a physical office people far away will start working late hours to keep up with the main office.
YMMV, but it's 3 AM here in Berlin and until 10 minutes ago I was still actively working.
I've been full-time remote for just shy of 5 years and timezones is definitely an issue. Up to 4 hour difference is sustainable indefinitely, 8 hours can be with the right people (doing split days is great for this), but beyond 8 hours and the amount of effort required for synchronous communication (video calls) causes it to not happen and the team loses cohesion.
You need the synchronous communication to have non-work conversations, and you need those non-work conversations to develop and maintain the relationships required (trust, rapport, etc.) for remote work.
> if your organization ever becomes big enough to warrant a physical office
...then you probably don't have enough buy-in to be a fully remote company and that is far harder to work around than timezones.
Yeah and the longer they stay up, the better as every few hours they calculate the total score which then gets averaged out over the course of a week I think.
I played a few years back, just by bike. But players in cars would always be quick enough to take down what I built.
As a rural player that lives in the city nowadays, I don't even feel remotely interested anymore as you can't impact the scores as much as you can in a rural area.
PureVPN because they have lots of countries to connect to. Albeit some sites using a different geolookup library don't actually recognise them accurately.
Reason? My ISP modem basically dies when there's too many connections opened at once. So sometimes an innocent `npm install` would kill my internet for a minute...
Uber uses SCIP as part of the LSP implementation for our Java monorepo (Pieces of which we've [open-sourced](https://github.com/uber/scip-lsp)). Standardizing on SCIP has helped us generalize tools to be independent of the compiler/language ecosystem (eg we could do call-stack-analysis on any project that exports valid SCIP; do feature flag cleanup; find refs/impls across a wider scope than most LSP servers can handle due to memory constraints).
reply