惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
雷峰网
雷峰网
Recent Announcements
Recent Announcements
月光博客
月光博客
G
Google Developers Blog
腾讯CDC
S
Secure Thoughts
大猫的无限游戏
大猫的无限游戏
T
Tenable Blog
云风的 BLOG
云风的 BLOG
W
WeLiveSecurity
博客园 - 【当耐特】
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
博客园 - 聂微东
The Cloudflare Blog
阮一峰的网络日志
阮一峰的网络日志
人人都是产品经理
人人都是产品经理
P
Privacy International News Feed
MyScale Blog
MyScale Blog
K
Kaspersky official blog
T
The Blog of Author Tim Ferriss
Attack and Defense Labs
Attack and Defense Labs
Spread Privacy
Spread Privacy
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
aimingoo的专栏
aimingoo的专栏
I
Intezer
Vercel News
Vercel News
小众软件
小众软件
Simon Willison's Weblog
Simon Willison's Weblog
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
N
Netflix TechBlog - Medium
P
Proofpoint News Feed
Latest news
Latest news
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
T
Tor Project blog
S
Security Affairs
P
Proofpoint News Feed
博客园 - 三生石上(FineUI控件)
博客园 - Franky
C
Cyber Attacks, Cyber Crime and Cyber Security
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
美团技术团队
Recent Commits to openclaw:main
Recent Commits to openclaw:main
S
Security @ Cisco Blogs
L
LINUX DO - 热门话题
Know Your Adversary
Know Your Adversary
Project Zero
Project Zero
D
Docker
L
Lohrmann on Cybersecurity
F
Full Disclosure

oida.dev | TypeScript, Rust

TypeScript's `erasableSyntaxOnly` Flag Unsafe for work Tokio: Macros Tokio: Channels Tokio: Getting Started Network Applications on the Tokio Stack Remake, Remodel, Reduce. The `never` type and error handling in TypeScript 5 Inconvenient Truths about TypeScript Refactoring in Rust: Introducing Traits Refactoring in Rust: Abstraction with the Newtype Pattern Announcing the TypeScript Cookbook TypeScript: Iterating over objects The road to universal JavaScript 10 years of oida.dev Rust: Tiny little traits The TypeScript converging point How not to learn TypeScript Getting started with Rust Introducing Slides and Coverage TypeScript: The humble function overload TypeScript + React: Children types are broken TypeScript: In defense of any Rust: Enums to wrap multiple errors Dissecting Deno Error handling in Rust TypeScript: Unexpected intersections Upgrading Node.js dependencies after a yarn audit TypeScript: Array.includes on narrow types TypeScript + React: Typing Generic forwardRefs shared, util, core: Schroedinger's module names Learning Rust and Go TypeScript: Narrow types in catch clauses TypeScript: Low maintenance types Tidy TypeScript: Name your generics Tidy TypeScript: Avoid traditional OOP patterns Tidy TypeScript: Prefer type aliases over interfaces Tidy TypeScript: Prefer union types over enums My new book: TypeScript in 50 Lessons Go Preact! ❤️ this in JavaScript and TypeScript TypeScript and ECMAScript Modules TypeScript + React: Why I don't use React.FC TypeScript + React: Component patterns TypeScript: Augmenting global and lib.dom.d.ts Vite with Preact and TypeScript TypeScript: Union to intersection type 11ty: Generate Twitter cards automatically Are large node module dependencies an issue? TypeScript: Variadic Tuple Types Preview TypeScript: Improving Object.keys Remake, Remodel. Part 4. TypeScript + React: Typing custom hooks with tuple types TypeScript: Assertion signatures and Object.defineProperty TypeScript: Check for object properties and narrow down type Boolean in JavaScript and TypeScript void in JavaScript and TypeScript Symbols in JavaScript and TypeScript Why I use TypeScript TypeScript + React: Extending JSX Elements TypeScript: Validate mapped types and const context TypeScript: Match the exact object shape TypeScript: The constructor interface pattern Streaming your Meetup - Part 4: Directing and Streaming with OBS Streaming your Meetup - Part 3: Speaker audio Streaming your Meetup - Part 2: Speaker video Streaming your Meetup - Part 1: Basics and Projector TypeScript and React Guide: Added a new styles chapter TypeScript and React Guide: Added a new render props chapter TypeScript and React: Styles and CSS TypeScript and React TypeScript and React Guide: Added a new prop types chapter TypeScript without TypeScript -- JSDoc superpowers TypeScript: Mapped types for type maps JAMStack vs serverless web apps The Unsung Benefits of JAMStack Sites TypeScript: Ambient modules for Webpack loaders My most favourite talks in 2018 TypeScript and React Guide: Added a new context chapter TypeScript: Built-in generic types TypeScript: Type predicates JSX is syntactic sugar TypeScript and React Guide: Added a new hooks chapter Getting your CfP application right FAQ on our Angular Connect Talk: Automating UI development TypeScript and Substitutability Debugging Node.js apps in TypeScript with Visual Studio Code From Medium: Deconfusing Pre- and Post-processing From Medium: PostCSS misconceptions Saving and scraping a website with Puppeteer Cutting the mustard - 2018 edition Wordpress as CMS for your JAMStack sites My most favourite podcast episodes in 2017 My most favourite talks in 2017 My most favourite books in 2017 The Best Request Is No Request, Revisited Not so hidden figures - Organizing ScriptConf My podcast journey to ScriptCast Grid layout, grid layout everywhere! #scriptconf and #devone
Topconf Linz 2016 is a wrap
2016-02-05 · via oida.dev | TypeScript, Rust

So, Linz has a software conference. One that’s supposed to stay. I think it’s about time. Linz has a wonderful IT community, with lots of great companies and so many schools and universities specialised for software development. Except for the short-lived Kod.io movement (spanning Kod.io, Codefront and Railsgirls in 2014), as well as some Linuxwochen now and then, I hardly can remember any full-fledged Software conference. So hey, we finally got one!

Usually I would give some sort of review. But as I was partly involved with the conference’s organisation, I decided to put a little twist on the usual review you would expect. As people recognised my involvement, they asked me a lot of questions around the conference in-between sessions. I gathered (or rather: remembered) the few questions attendees asked me the most.

Why did you organise the Austrian Topconf in Linz? #

First of all: I’m not the organiser. Chris Frei from Topconf is, I’m “just” in the program committee. This put me in a wonderful position of being able to wish for incredible speakers and create some wonderful tracks. When I see Ben Reitzammer say on Twitter that “Your program committee did really great work to put together a diverse program & set of speakers! Very well done!”, I feel both flattered and happy.

How Topconf came to Linz was partly my fault. I spoke at Topconf Tallinn back in 2013. Chris Frei wanted to expand from Estonia to other countries in Europe and asked me where to organise one in Vienna, and which companies to contact. I quickly could convince him that I just know about the IT scene in Linz, and that Linz would also be a good place to have a conference. I quickly gathered some people who would join the program committee, and that’s how it came to be.

Some attendees said that it “was about time” that Linz got its own conference. And I think they are right.

How did you get Harry Roberts to speak?!?! #

I asked. And since he’s really a nice guy, he actually came! Same goes for Kahlil Lechelt, Henning Glatter-Götz, Rachel Andrew, Eva-Lotta Lamm, Phil Nash, and Mario Heiderich. And I’m so incredibly thankful that they all agreed to join. They are fantastic speakers and brought real value to our little event. Lots of attendees really appreciated having them at the conference.

This goes also for Tim Perry, Alessandro Canessa and Martin Naumann who joined through our Call for Papers. So much valuable content and so much fun having you guys here.

Seriously, what happened with the catering? #

It was quite a catastrophe, wasn’t it. Well, those are the parts where not being an organiser really sucks. Honestly, I don’t know what happened. We had a great catering service first, but for some reasons they had to drop out on short notice. About 8 days before the event. And I still don’t know why. The alternative would’ve been two days and one night of McDonalds. This was the first time where the program committee, especially Lisi, David and me, were dead against.

What came then wasn’t much better. Instead of two days, one night, we got one night and some rather effortless alternative delivered by the venue. Heavy meaty. I would have loved some progressively enhanced food: Vegetarian first, meat as an extra.

We will definitely take care of this issue the next time. With Chris not being a Linzer, it’s hard for him to get to the right addresses on his own. This is something that we from the program commitee should’ve kept an eye on. Think about you organising a conference at some place you rarely be, relying on Google and some recommendations? We will hook him up with the right people to get some proper and delicious food the next time. We already have some providers in mind.

The beer was excellent, though.

Cool, any last words? #

Yes. A lot of "thank you"s. Thanks to my wonderful colleagues who made this event possible: Jürgen, Tom, Lisi, David, Andi, Bräusi and Wirthi.

The wonderful speakers who came: Eva-Lotta, Harry, Rachel, Tim, Martin, Mario, Phil, Alessandro, Henning and Kahlil.

My former client “BGT”, who sponsored the event and had some great time with us. My current employer Dynatrace who sponsored, and all my colleagues who came to the event. Speaking to you in-between sessions was valuable and immediate feedback to react quickly.

All the attendees who joined us at the conference, at lunch, at the bars. Seeing you all engage in wonderful discussions and having so much fun together was constantly telling me: Totally worth it. Glad that you enjoyed being here.

And last, but not least: To Chris and Laura. You put so much effort into giving our community a great event and gave us such a wonderful time. Thank you for everything. On 2017!

Related Articles