Oh, just manual template typing. That's not great. We've done that and it is error-prone. A SQL-generator infers the types from the query, for example.
That's the raw, raw querying. They provide a TypedSQL system where you write SQL and it automatically generated the parameter and return types. It's in the docs.
I've been using v2 for a month or so and it's really great. There are a few things that feel a little bit rougher than the Rust equivalent (Tauri), but Go is just so much faster to code in that this has been a pleasure to work with.
Also props to the lead maintainer Lea Anthony who seems to be behind all the very exciting momentum of the project
What would be the main differences Wails and Tauri? Rust's gurantees regarding type safety and parallelism? I image that the performance characteristics greatly depend on the chosen front end framework, or am I mistaken here?
I can only speak on Tauri, which I’ve been using to build a video editor, but with most of the heavy code living on the Rust side, the UI remains snappy and responsive even while the “backend” is seeking through videos or whatever.
I’m using Svelte, but I don’t think that matters too much. The popular front end frameworks are close enough in performance IMO. I think it would really come down to dividing up the operations so the expensive ones run in native code instead of JS.
I have discussed this idea with friends who are writers / artists. Call me a cynic, but while many writers / artists aspire to collective shared knowledge, the reality of both the writing and art market is that unique knowledge is an important differentiator and an asset to their careers. If you do find a fascinating, rare 19th century travel journal in some online archive the last thing you are going to do is share it with others like you until you're sure that you're not going to use it as material yourself. The exception to this being other writers completed work (ie long-form articles, books), but that probably doesn't need a focus on writers / artists per se and a more general "aesthete" HN might work better...
That's not my experience at all. I am trying to start a new career as a fiction writer, and writers are very interested in sharing knowledge. I say this for both professional, published authors and wannabes like me.
I was part of a long creative writing course (about 9 months), and our class of 20 formed a bond of helping each other A LOT. Sharing tips, beta reading, posting about prizes, open calls for literary magazines, etc.
In this class, we decided to start inviting published authors to share tips for beginners. We got mostly positive responses. Professional writers would spend about 2 hours with us (online) sharing tips and answering questions. All of them were very transparent about how they write and gave useful tips on how to get published. They said things that would be impossible to learn without talking to a professional author.
So I call you a cynic, as you asked me to, and a wrong one at that.
To understand this more fully you’d need to appreciate two things.
One is that while there are a lot of things that people will share with you (they often want to share their expertise/craft and be good humans), there are a number of things they won’t share with you.
Two is that when you are starting out you are in a position where almost all information from an experienced artisan is helpful. That can mean you may easily miss what they are not telling you.
This is not to say they are misleading you or hold ill will because the information they withhold from the conversation would not be useful to you anyway, as you are not in a position to use it or be a threat to them.
Or, the alternative, is that yours (apparently) and gp’s point of view is not that common as you think it is. So it is not me that have to understand things, it is you that are wrong.
Also, the mentioned example seems very implausible. What makes an author unique is not what source they used for inspiration. Two writers will get the exact same “19th century travel journal” and write to completely different stories inspired by it. In different genres most likely.
I don’t think our points are opposed. I can’t speak for the parent but I am not saying people don’t like you, won’t help you or that they resent you or guard their secrets. They can like you and not tell you important points they’d like to keep secret.
I am saying that if you went in asking certain direct questions about the author’s work you wouldn’t get the same reception.
I agree with your point about the outcome of discovering a journal in a broad sense but think reading parent’s example accurately requires a lot of context of being in the industry, presence at the right events, and knowledge of the zeitgeist. There is still competition.
I think they are opposed. Writers hiding research secrets because they don't want to help the competition seems to be as useless as wannabe founders hiding their idea for a business because they are afraid someone will steal them. It is much more likely that this secrecy is hurting more than helping them, as they don't have some feedback on how to improve the idea.
Also, the existence of secrets among humans due to competition seems to be a moot point. Bringing the discussion to the original point, if said competition prevents the existence of a writers' HN, I believe that is completely false. HN is good for entrepreneurs. The fact that they don't share their sales leads here doesn't matter at all for the existence and quality of HN.
Totally disagree with your first point. It is only valid if you have infinite money and all the best connections and perfect trust. Show me where that exists and I’ll buy it.
Hiding the right secrets in an early company is critical, whether they are technological that you are hiding from competitors or business plan endgames that you are hiding from customers (but perhaps you aren’t aware of them and only the VC sees it). There is a big difference between some person thinking they have a great idea but won’t tell anyone, and determining where you draw the line on sharing product, go-to-market, etc. People who raise enough money have the “that’s the secret part” point of the conversation. The conversation goes better if they communicate that in a way most people don’t notice, though, and so at that point they frequently redirect, deflect or defer.
I think we see the audience of HN differently — from my perception it is predominantly aspirational entrepreneurs, not actual entrepreneurs that make up the majority of engagement here. While no doubt the percentage of entrepreneurs is higher here than just about anywhere else, entrepreneurs have less time and there are just far fewer of them. What I believe is predominant here though, whether entrepreneur or not, is engineer/developer roles.
Regarding your point on competition I think we understand the two cultures of engineers and writers differently. Writing has less constraint, and in my experience that means it is more reliant on ego expression. It can be humbling but a person can also make a great career being a terrible writer. Engineers make things that function. If you are a terrible engineer, your work will rapidly disappoint probably a lot of people, and either you improve, you hide somewhere adjacent, or you leave the profession.
I think HN works for a variety of reasons including the general humility of engineers, the general lack of desire for the spotlight, and the frequency of dramatic and immediate improvement of workflows due to new tools. I don’t know which of these and other reasons are critical but I am skeptical writing has enough of them. Maybe with a new generation of writers.
This is not how fiction writing works, specifically. The hugest fans of fiction writers are other fiction writers. There is a desire by writers to see every other writer succeed just because they love seeing others' work. In my subfield, multiple award-winning authors have rescinded their candidacy for internationally-recognized awards simply because they want other authors they're a fan of to get the spotlight instead.
Yes I think that's fair especially about writing technique if that was the OP's original analogy, and in particular about new writers as you point out.
What I was referring to specifically was inspiration and knowledge of niche events that become the details that bring prose / art alive. These immediately lose their effect if they are reused which is why my friends who are professional writers dedicate an enormous amount of time to research in the hope that these details may jump out to them.
In a lot of contemporary art, a curator's view of work is often hung around a particular piece of research and that must be unique to warrant the attention of the public - my original point was that that research just can't be shared until the work is revealed.
However, maybe to your point, there is a lot of value in a more technical literary HN which encourages meta discussion on the process of writing rather than the content.
I've never saw a software engineer hoard some knowledge for a competitive edge. I guess it's blue/red ocean market difference multiplied by the fact that average engineer can feel pretty successful with his career, whereas an average writer is anything but.
Even in writing, the right combination of execution and being in the right place at the right time is everything, and ideas/knowledge/concepts are like sand at the beach. But yeah like all art "markets" it's massively unevenly distributed, so you'll find way more people who are cynical about it.
If you are an essential part of your startup as, for example CTOs are in very early stage startups, you may find it difficult to completely detach for more than a few weeks especially if the business is negotiating a complicated part of its development.
There is much good advice here but I would add a few things that I have not seen in other comments. My advice is not for people who are employees as I believe they should take at a minimum their entire statutory allowance, but for founders with a greater stake in the success of the business:
- although the first few weeks are certainly the most challenging especially if you end up staying on in hospital for a few days, there will be many challenges over the entire first year unless you have excellent family (ie grandmother) help - so pace yourself and your team's expectation of your involvement.
- Plan to be completely absent for the first few weeks and adjust your team's expectations accordingly, but then optimise asynchronous communication of all but the most pressing issues from that point on. This helps if your business is remote because it's likely you will already be successfully using asynchronous communication through tickets / slack / email.
- While it would have been great to spend my downtime watching series, early infancy tends to give you a lot of time at unexpected hours and it can actually end up being quite painless to put in 2-3 hours of problem solving or pull request reviews. These can make the difference between a team heading radically off path and staying on track.
- If you can (ie if you're not the one breastfeeding -- that's totally consuming and you won't be able to do anything) try and distribute some of your leave later because babies get more engaging every extra day they are out of the womb!
If Rust is too much of an adventure, maybe you'll find Go easier. Wails [1] is great if perhaps a bit more rough round the edges. Because it's go, package sizes are 10mb+ but nothing like Electron 30mb+
It is easy to agree with the sentiment of this article, but the fundamental premise of this is wrong in modern architecture. That premise is that it is the architect that is in control of the final aesthetic of the building. Architects get work by participating in competitions against other architects for limited budgets. In a few, rare cases (usually public buildings and museums) an extraordinary budget may be approved that goes to funding truly radical buildings that break from the status quo, but in the overwhelming majority of cases architects play a fine line within the following constraints:
1. Planning regulations (in the UK at least, it's very hard to propose buildings that differ significantly from neighbouring buildings)
2. Materials -- building custom window frames / door frames is incredibly expensive. The first thing that tends to get cut as budgets are inevitably squeezed are any custom items
3. Client expectations -- most new large buildings are built with a projection of future occupants. Developers want to be able to make apartments as saleable as possible so usually take the most risk-averse options
While I applaud concepts with more colour, detail and originality, you must also consider where you would like to live. Most people (I think) want to build out their own custom surroundings as their home grows on them. Bland buildings make this easier because it is a blank canvas upon which you can begin to construct your own projection of your ideal home. Being locked inside a giant multicoloured artwork conceived of by somebody else might sound appealing to start off with, but will quickly become an aesthetic prison of somebody else's personality.
> That premise is that it is the architect that is in control of the final aesthetic of the building.
I disagree.
The article frames the question by examining what kind of work architects celebrate and award. It doesn't matter who had the final say in any given design or even all the designs; architects, not client expectations, are responsible for what kind of work gets the Pritzker prize.
For anybody thinking about contributing this, this is sadly as close to not open source as open source gets. I tried to contribute to this, but it's impossible to build without the webrtc binary and the docs are deliberately opaque about going about building your own version of the binary. You are encouraged to pay the (almost sole) contributor of this repo for his build of webrtc. For this reason it's not really surprising that this version is both quite out of sync with the mainline OBS and also has only one or two contributors. Fortunately, for me, most plugins built with the mainline OBS do work with this.
I get that the maintainer has put a lot of work into this and wants to try and monetize some part which is hard when OBS is GPL, but depending on a binary which is nigh-on impossible to build and then charging for it on your website just feels a bit of a shitty way to do it.
I've been using this for nearly a year and it's by far the best thing I've found so far for testing realistic websockets load where servers are put under strain not just by connections but interactions between each other. Many thanks for the dev team behind this. It's a great piece of work.
+1 for Eça de Queiroz. With the exception of O Crime do Padre Amaro which can in places be a bit blunt, he tends to have a a kind admiration for his characters as he quietly makes fun of them and the decadent society around them.
prisma.$queryraw<YourType>`SELECT * FROM ...`