kenshaw

8 ms·

1.
by kenshaw 1y ago
I encountered this while trying to issue a new certificate for a service. As a temporary fix, started using ZeroSSL which conveniently also supports the ACME protocol. While not a big problem, if you have something like `cert-manager` being
2.
LetsEncrypt Outage(letsencrypt.status.io)
185 points by kenshaw 1y ago|107 comments
3.
by kenshaw 4y ago
Thanks, appreciate the package. I submitted a PR as I was also looking for a Go package similar to this, and wanted to make using this as a library a bit easier. I plan on using this to automate some website login/authentication flows,
4.
by kenshaw 5y ago
discord.
5.
by kenshaw 5y ago
I'm the author of xo. I appreciate the reference here, but that's not really what xo does. It generates all boilerplate for you directly based on whatever is defined by the database. It doesn't do anything with YAML, nor does
6.
by kenshaw 5y ago
That's cool. As per the other comment, you should share it with the community.
7.
Usql v0.9.4(github.com)
2 points by kenshaw 5y ago|0 comments
8.
by kenshaw 6y ago
A long overdue release. General bug fixes, \d* commands, new database support, and a native Oracle driver.
9.
Usql v0.8.2(github.com)
4 points by kenshaw 6y ago|3 comments
10.
by kenshaw 7y ago
Foreign keys should definitely be used in most schema designs. While I can agree that they are problematic when doing a schema migration, a schema migration would only happen "very rarely" whereas inserts/deletes happen regul
11.
by kenshaw 7y ago
I disagree, and history does not show this to be true. We have been more fickle when it comes to instant messengers than almost any other technology on the face of the planet (pun intended). From IRC, ICQ, AIM, Facebook messages on the webs
12.
by kenshaw 7y ago
I appreciate your response, and will give you the benefit of doubt -- however this is in conflict with what a superficial reading of Schneiner's article suggests. Reading the reporting it would seems to indicate that this is happening&
13.
by kenshaw 8y ago
Yes, I understand how this would be done. It's a design philosophy. If you'd like Gunk to support "oneof", we're open to Pull Requests!
14.
by kenshaw 8y ago
Gunk is a frontend to protoc. If one needs to use "oneof", it's still possible to just define it in a .proto file. Gunk interoperates cleanly with both .proto and .gunk files.
15.
by kenshaw 8y ago
lowmagnet more or gave a succinct summary. I've also now added other comments here, discussing my views. I don't believe it's necessary, and I would proscribe other ways to accomplish the same design. It's a philosophy o
16.
by kenshaw 8y ago
I feel very strongly that type safety is of paramount importance in development, and "oneof" (and other similar constructs) in protocol design breaks fundamental ideas of type safety. It's a feature of the IDL that doesn&#x27
17.
by kenshaw 8y ago
In proto3 all fields are optional. As such, I don't see the need for "oneof" since you should check in business logic whether or not the field is there. By using "oneof" you are declaring two different types can be
18.
by kenshaw 8y ago
I haven't specifically looked at the Kubernetes code base, but I will -- thanks for the pointer! We plan to expand / support / better standardize the annotations in the github.com/gunk/opt package in time.
19.
by kenshaw 8y ago
Yes, this has the added benefit of standardizing protocol buffer based workflows across teams / repositories. I appreciate the criticism, but we (the Brankas developers) find this syntax significantly easier to use, as well as the tool
20.
by kenshaw 8y ago
There is an explanation in the README file, but I'll explain: It helps to standardize workflows across a number of different source repositories (all Go based), where a number of different developers had come up with different ad-hoc w
21.
by kenshaw 8y ago
Thanks for the input -- this actually does support enums, using a variant of Go's const: type MyEnum int const ( MYENUMVAL MyEnum = iota ) It's a philosophical argument, but one should not design a protoc
22.
by kenshaw 8y ago
We just pushed the first initial, public release of Gunk, a modern frontend and syntax for Protocol Buffers. Check out releases here: https://github.com/gunk/gunk/releases/tag/v0.1.0 Please note this is
23.
Gunk: Modern front end and syntax for Protocol Buffers(github.com)
73 points by kenshaw 8y ago|39 comments
24.
by kenshaw 8y ago
Yes, it reads from STDIN. If it doesn't, it's a bug, and please file an issue on GitHub.
25.
by kenshaw 8y ago
This is a syntax highlighting issue, most likely. The \ commands are not highlighted. Are you using a white or light colored background? Likely the contrast isn't high enough. I just updated the documentation with more information on c
26.
by kenshaw 8y ago
I think they're saying "SEQUEL", which is the widely accepted/recognized pronounced mononym for "SQL".
27.
by kenshaw 8y ago
Yes and no. ODBC on Windows may (or may not) be provided by the Microsoft JET driver, which can be considered a database unto itself. Specifically, there is a separate ODBC driver for Go that usql supports, which is what this is reflective
28.
by kenshaw 8y ago
As what amjith said -- however, I personally find myself working with upwards of 3+ different databases in a single day. I may not be the use case, but eventually I realized it would have been easier to write a single, consistent client tha
29.
by kenshaw 8y ago
It's more of a passionate side project at the moment, as I am still reverse engineering the protocols involved. It's not close to completion, but I'm hoping to have it done sometime in the next few months. It's not a hi
30.
by kenshaw 8y ago
Yes, I've been working on a 100% native Go driver for Oracle. It is not even alpha or beta quality at this time.

More ›